shailendra333 / webutilities

Automatically exported from code.google.com/p/webutilities
0 stars 0 forks source link

ResponseCacheFilter does not cache correct content when original filter calls no setStatus() or sendError() methods #48

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. chain the filters so that ResponseCacheFilter caches other filter result, 
e.g. css files, but calls no response.setStatus() or sendError() methods
2. call the css url
3. the result does not get cached inside ResponseCacheFilter - only "200 OK" 
results get cached

What is the expected output? What do you see instead?
the result is cached same as 200 OK results

What version of the product are you using? On what operating system?
0.0.6

Please provide any additional information below.
related to #35, that prevented it from being served through apache.

Original issue reported on code.google.com by jindrich...@gmail.com on 26 Apr 2013 at 1:32

GoogleCodeExporter commented 9 years ago

Original comment by rr.patil...@gmail.com on 22 Aug 2013 at 12:14

GoogleCodeExporter commented 9 years ago
https://github.com/rpatil26/webutilities/commit/9f570373e300bdb08a7c476f441cfb2a
6827a992

Original comment by rr.patil...@gmail.com on 9 May 2014 at 2:07