Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Cache-Control: no-transform has no effect if combined with other values #863

Closed
GoogleCodeExporter opened this issue Apr 6, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

According to the documentation it should be possible to deactivate 
mod_pagespeed by sending a Cache-Control: no-transform header. 

This works as expected but if you combine no-transform with other values, 
mod_pagespeed ignores it. eg.: 

Cache-Control: no-cache, private, no-store, must-revalidate, max-stale=0, 
post-check=0, pre-check=0, max-age=0, no-transform

or

Cache-Control: no-cache, private, no-store, must-revalidate, no-transform, 
max-stale=0, post-check=0, pre-check=0, max-age=0

it only works if you add multiple Cache-Control headers to the response. 

What steps will reproduce the problem?
1. Send the following header: Cache-Control: no-cache, private, no-store, 
must-revalidate, max-stale=0, post-check=0, pre-check=0, max-age=0, no-transform

What is the expected output? What do you see instead?
mod_pagespeed should be deactivated. 

What version of the product are you using (please check X-Mod-Pagespeed
header)?
1.6.29.7-3566

On what operating system?
Debian 7.2

Which version of Apache?
Apache/2.2.22

Which MPM?
ITK

URL of broken page:
None


Original issue reported on code.google.com by [email protected] on 8 Jan 2014 at 2:05

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant