https://bz.apache.org/bugzilla/show_bug.cgi?id=58009
--- Comment #3 from Mark Thomas <ma...@apache.org> --- 'Not found' results are cached as well. I suspect the application code is checking that the file exists, discovering that it doesn't (which is cached), ading the file (outside of the WebResources impl) and the trying to access at which point it is seeing the cached 'not found' response. It may be possible to fix the application to avoid triggering the addition of the resource to the cache as 'not found'. Maybe the answer is extending the WebResources API to include creation of resources. There are probably other solutions as well. A simple test case that demonstrates the issue would enable us to evaluate the different possible solutions. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
