When JSCSSMergeServlet returns a Not Modified, cache headers (if any) are not set

GoogleCodeExporter commented 9 years ago

I'm not sure if this is a feature or a bug but I have set my servlet to use a 
2h expiry and during the first 2h, my browser doesn't request the resources any 
more (which is fine). Then after the 2h, my browser requests the resource and 
gets a not modified response. From this point onwards, the browser keeps 
requesting the resource over and over again - and keeps getting a not modified 
response. The cache headers are not set by the servlet when a not modified 
response is returned.

Original issue reported on code.google.com by nlesc...@gmail.com on 26 Apr 2012 at 3:01

GoogleCodeExporter commented 9 years ago

Original comment by rr.patil...@gmail.com on 30 Apr 2012 at 5:37

Added labels: Milestone-0.0.6

GoogleCodeExporter commented 9 years ago

https://github.com/rpatil26/webutilities/commit/29f5ce91daa53d53148352a3635126a9
e211e306

Need to check and confirm

Original comment by rr.patil...@gmail.com on 22 Feb 2013 at 9:51

Changed state: Fixed

prabhuish / webutilities

When JSCSSMergeServlet returns a Not Modified, cache headers (if any) are not set #36