-
-
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
add etag support at the http level #1183
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a great, and simple, addition
templates/conf.d/nginx.conf.erb
Outdated
@@ -96,6 +96,10 @@ http { | |||
lingering_timeout <%= @lingering_timeout %>; | |||
tcp_nodelay <%= @http_tcp_nodelay %>; | |||
|
|||
<% if defined? @etag -%> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<% if @etag -%>
is fine here since etag is either undef
or a yes\no
string, not a boolean.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing. I just pushed a fix for this, along with a small formatting change for the whitespace so the config file will not get an extra newline when no value is set.
c9d6d93
to
4e9cd6e
Compare
@bryangwilliam Thanks! |
add etag support at the http level
add etag support at the http level
This change adds support for enabling/disabling the etag nginx directive in the http context. http://nginx.org/en/docs/http/ngx_http_core_module.html#etag
If no value is supplied it will not add anything and allow the nginx-defined default to take effect.