Bear Bibeault wrote:Open the browser tools and observe the behavior of the Network tab. What's happening?
Bear Bibeault wrote:Then it is likely that whatever is responsible fro making the request may no be doing its job,. Usually even cached responses are shown in the panel.
Bear Bibeault wrote:Not seeing anything there that should trigger a new servlet request.
Bear Bibeault wrote:What makes that request?
Bear Bibeault wrote:So you are saying that when the JSP is displayed, a request to the image src is not made?
You could try the old trick of adding a random number as a request parameter just to see if it is indeed a caching issue.
Bear Bibeault wrote:... or JavaScript.
Bear Bibeault wrote:Yup, that should do it. Does it solve the issue?
If it does, you know you've got a caching issue. You can investigate why your caching directives aren't working (or leave the work-around, which is a bit grody, but no less used for all its grodiness).
Dave Tolls wrote:Your caching directive only affects the page.
It does not affect the <img>'s that the page pulls back.