have you implemented HttpServer.getLastModified(HttpServletRequest req)?
Try returning -1, this should tell the browser that the requested resource
should not be cached.  This is the default behaviour, so you might try
returning the actual current time, this will tell the browser that the
resource has changed with each request, and it shouldn't use the cached
response.

See
http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpSe
rvlet.html

Lance

----- Original Message -----
From: "Todd McGrath" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, May 30, 2001 1:24 PM
Subject: image/servlet caching issue


> I'm having what I believe to be a image/servlet issue cache issue with
Orion
> 1.4.5:
>
> Situation:
> I'm creating dynamically generated graphs based on an authenticated
user.
> The images are created by passing values to a graph generating servlet.
>
> HTML looks like this:
>
> <img border="0"
> src="/Incentive1Graph?mgmt01=37500&min=10009&target=25024&gold=37535">
>
> where Incentive1Graph is a servlet that produces the image based on
mgmt01,
> min, target and gold values.
>
> The very first time the servlet is run it produces the correct image.
> However, on any subsequent calls with a different user, the original
image
> is returned.  I think the image/servlet is being cached by Orion and
thus,
> always returns the first image that was created.  If I restart Orion,
log in
> with a different user, the image produced is correct.
>
> Here's what I've done to debug so far:
>
> 1) Verfied the values for mgmt01, min, etc. are changing with different
> users
> 2) Deleted all files in the persistence directory
> 3) Deleted my browser cache
> 4) Tried with both Netscape and IE
> 5) Verified that I'm not accessing the test site through a proxy
> 6) Searched the Orion mailing list for similar issues
>
> Any other ideas???
>
> My questions are:
> 1) how do disable image/servlet caching in Orion config?
> 2) is there something I can write in the Incentive1Graph servlet that
will
> prevent it from being cached?



Reply via email to