-
-
Notifications
You must be signed in to change notification settings - Fork 883
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
Incorrect default timeout values #1137
Comments
I'd prefer adding the |
Done :) |
I'm confused. |
Fixed in #1138 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
class { 'nginx': }
What are you seeing
/etc/nginx/nginx.conf is created with (among some other config) these values:
keepalive_timeout 65;
client_body_timeout 60;
send_timeout 60;
lingering_timeout 5;
What behaviour did you expect instead
We had an issue that we are seeing HTTP 499 errors (client timeout) for requests that dont take very long (eg. only few hundred ms). I noticed there is no indication of what exactly the '65', '60' or '5' is. What I mean by that is that it does not indicate whether it are seconds, minutes, hours or whatever.
When I change the configuration to:
The change becomes:
And all HTTP 499 timeouts are resolved.
Any additional information you'd like to impart
Looking at the nginx source code it seems to me the values are interpreted by default in miliseconds, eg. the source shows:
Thus, the Puppet module should add 's' to all values or increase the default values by 1000.
Also, the Nginx documentation has all default values explained in seconds. For example see the following snippet from:
http://nginx.org/en/docs/http/ngx_http_core_module.html#send_timeout
The actual issue:
It seems that the Puppet module should indicate timeout values with an 's' suffixed to all default values to indicate seconds. The default (without any suffix) seems to be in miliseconds. The nginx call 'ngx_conf_merge_msec_value' seems to support this.
The text was updated successfully, but these errors were encountered: