-
Notifications
You must be signed in to change notification settings - Fork 363
POSITION_AUX=true broken in nginx 1.9.11+ #1154
Comments
I can confirm this with Nginx 1.19.6 as well: adding
…which might explain why #612 is still open despite #906 and #1155. |
I remember that the POSITION_AUX feature didn't seem to get any traction or testing feedback, or at least the large majority users didn't seem to need it. The plan was to get some feedback on the feature and then flip the switch after building some confidence through that, as the change itself is simple but its implications may not be. See this (6 year old :-) ) [PR review discussion] (#906 (comment)). |
My main use for it would've been to restore mod_headers_more's ability to suppress Nginx's native |
I just dug a little deeper and actually ngx_pagespeed is removing all our custom headers from our responses, both those set with Does nobody else in production need to set any header in Nginx? |
That does seem unlikely to me. Does this happen only with |
I tested it with plain image URLs when pagespeed is on. My work-around for now (which turned out to work quite well) is to have Nginx proxy into itself to a private port on the paths I want PageSpeed involved, so I can massage the headers before they go out. The inside server enables PageSpeed and the outside one doesn't. |
That's one way to solve the problem :-) Now if you could configure thenreverse proxy to cache .pagespeed. resources, you might actually get something else out of it too, and minimize the incurred overhead. (note caching the html is tempting, but harder to set up correctly, but just the |
Setting
POSITION_AUX=true
is not working in nginx 1.9.11+. The modulengx_pagespeed
is appearing in bothHTTP_FILTER_MODULES
andHTTP_AUX_FILTER_MODULES
.ngx_pagespeed
is appearing by default inHTTP_FILTER_MODULES
. WhenPOSITION_AUX=true
, the default entry needs to be removed before it is added toHTTP_AUX_FILTER_MODULES
.The text was updated successfully, but these errors were encountered: