-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Note about the Keep Alive
Apache example
#252
Comments
@alrra Same here. I will take a look and reply to you. Is it possible to you create a pull-request with your considerations ? |
Hey @alrra, thanks a lot for putting this together. Although this improvement looks useful, I prefer to remove the Server section because people will start to send tips for other servers like nginx and so on (why Apache only?). Perhaps we should focus on front-end and keep these server tips to another guide. |
@zenorocha SGTM. You should open an issue in that sense. :) |
The Keep Alive Apache example is wrong, as it just sets the header, but that won't make the server do what is expected.
The correct way of doing it is through the
KeepAlive
,KeepAliveTimeout
andMaxKeepAliveRequests
Apache core directives.These core directives won't work in the
.htaccess
file, however, Apache (v2.2.0+ at least):has (should have)
![](https://camo.githubusercontent.com/4fb51ceb41b54cb138dbe13625265b5cf621ae1fb1ac3e129f4441ebd21cbcaa/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f313232333536352f323036303431312f35356565313763322d386331362d313165332d393464332d3965643166373465313437652e706e67)
KeepAlive On
by defaultprovides (should provide) default values for the
KeepAliveTimeout
andMaxKeepAliveRequests
directivesSo, if
KeepAlive
is set toOff
, Apache not only won't do what is expected, but will also kinda overwrite (will appendclose
to) theConnection
header the user has set.The text was updated successfully, but these errors were encountered: