Re: Custom headers getting stripped by mod-pagespeed

[Joshua Marantz]

See: https://code.google.com/p/modpagespeed/issues/detail?id=730 which captures the fact that MPS strips 'nostore'.  We will stop doing that soon.

I don't know why X-UA-Compatible: chrome=1is being stripped; we are not trying to do that. Custom headers should be retained. What apache config settings were you using?

-Josh

On Wed, May 15, 2013 at 10:56 PM, Nathan <nat...@kurtykagroup.com> wrote:

When trying to add a "X-UA-Compatible" header (for ChromeFrame), I discovered that mod-pagespeed seems to be removing all custom headers.  

Below is a server response with and without mod-pagespeed:

?ModPagespeed=on

HTTP/1.1 200 OK Cache-Control: max-age=0, no-cache Content-Encoding: gzip Content-Type: text/html;charset=utf-8 Date: Thu, 16 May 2013 02:50:35 GMT Pragma: no-cache Server: Apache Vary: Accept-Encoding X-Mod-Pagespeed: 1.3.25.4-2941 Content-Length: 8817 Connection: keep-alive

?ModPagespeed=off

HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Content-Type: text/html;charset=utf-8 Date: Thu, 16 May 2013 02:52:41 GMT Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Server: Apache X-UA-Compatible: chrome=1 transfer-encoding: chunked Connection: keep-alive

Notice that only the "off" response contains the "X-UA-Compatible" header.  I'm adding the header with the following line in my .htaccess: Header append X-UA-Compatible "chrome=1".  

I searched these forums and found older mentions of similar bugs, but they all sound like they're fixed.  Help?

 

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Joshua Marantz]

Correction: we're tracking the 'nostore' and related bugs in issue 683, which is now fixed in trunk.

-Josh