Thanks for the replies. Hopefully this will help someone else now, or via
the archives: I misunderstood Netscape's cache options. I had it comparing
dates once per session, thinking it would not force an update except once
per session. Really it forces an update every time it is not making a
comparison. No If-Modified-Since header was going out. Now I now have
Netscape set to "compare every time".
Suzanne
At 09:20 AM 10/8/99 +1000, Geoff Soutter wrote:
>Suzanne Morine wrote:
> >What are people doing to make the browsers use the cache copy
> >unless the content is different than the last time? I am using
> >getLastModified to return the new time and the browser/servlet-
> >runner combination are not acting as expected. I could try all sorts
> >of combinations of things, but I thought I would ask how people
> >have done this sort of thing.
>
>Try checking the source for javax.servlet.http.HttpServlet. This contains
>the code that makes the decision to cache. If you "copy" this logic into
>your doGet() method, you can see and control exactly what is happening...
>
>Things i'd check are:
>- have you got your browser cache settings right?
>- does the VM that JRun is running under have the right time settings? If
>you're using the MSVM, it stuffs up timezones...
>- does JRun add any headers that affect the situation? you could try
>telnetting to the JRun port and doing a GET manually..., and try printing
>out all the headers in your servlet...
Suzanne Morine
ARITEK Systems, Inc.
[EMAIL PROTECTED] <http://www.aritek.com>
(303) 713-1401 ext. 311
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html