|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2548 | major | sometimes | 03-24-08 10:37 | 03-25-08 15:10 | |
|
|
|||||
| Reporter: | david-peterson | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.25 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.6 | ||
|
|
|||||
| Summary: | 0002548: jsp pages sometimes "stuck" in proxy cache | ||||
| Description: |
I think this is related to http://bugs.caucho.com/view.php?id=1992 [^] The fix for the above in 3.0.25 seemed to resolve the issue for all static content being served by the FileServlet (images, css, html, etc.) but noticed the same thing happening to certain JSPs that we have. Traced it down to only happening with really simple JSPs that were essentially purely static content. The generated .java file had the _caucho_lastModified() method filed with dependency tracking code instead of just "return 0" and this seemed to cause the caching code to generate ETag and Expires headers which didn't always get cleared out when the underlying JSP changed (or something). I was wondering if there was a similar bug in the JavaPage servlet as there was in the FileServlet regarding how cached files are managed. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||