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

Issue downstream cache purges only for GET requests. #752

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Apr 6, 2015

We should only convert GETs into PURGEs and not touch other request methods, 
because it is possible to have POSTs with response content-type as text/html 
and these should not be turned into PURGEs. We should also add something our 
documentation indicating that requests with non-GET HTTP methods should bypass 
the cache. 

As of now, PURGEs for POSTs should be effectively harmless 404s (assuming that 
POSTs are bypassed while caching). But, it is unnecessary work as far as the 
server is concerned.

Original issue reported on code.google.com by anup...@google.com on 26 Jul 2013 at 12:12

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Fix submitted as part of 
https://code.google.com/p/modpagespeed/source/detail?r=3912
Should be available in the next release.

Original comment by anup...@google.com on 3 Apr 2014 at 7:25

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmaes...@google.com on 30 Apr 2014 at 8:49

  • Changed title: Issue downstream cache purges only for GET requests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment