Thanks for reply, Kevin.
I find this all a little confusing. According to the HTTP spec, "Back"
buttons and history lists are supposed to ignore all caching instructions
and always get the latest image of the page form memory. Following is an
abstract form the HTTP spec
http://www.w3.org/Protocols/rfc2616/rfc2616.html, paragraph 13.13.
"User agents often have history mechanisms, such as "Back" buttons and
history lists, which can be used to redisplay an entity retrieved earlier in
a session. "
"History mechanisms and caches are different. In particular history
mechanisms SHOULD NOT try to show a semantically transparent view of the
current state of a resource. Rather, a history mechanism is meant to show
exactly what the user saw at the time when the resource was retrieved."
"By default, an expiration time does not apply to history mechanisms. If the
entity is still in storage, a history mechanism SHOULD display it even if
the entity has expired, unless the user has specifically configured the
agent to refresh expired history documents."
Am I wrong, or do both IE and Netscape appear to violate the HTTP spec?
_____________________
George Svedloff
[EMAIL PROTECTED]
http://www.liquidprice.com
1.800.863.2220
----- Original Message -----
From: Kevin Mukhar <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 08, 2000 6:44 AM
Subject: Re: "Back" button realoading a page - related to persistent cookies
> George Svedloff wrote:
> >
> > We are actually using WebSphere and IIS (and using
javax.servlet.http.Cookie
> > objects as well).
> >
> > I would guess that what happens is that WebSphere sets some haders in
the
> > Response that marks the page as non-cacheable. The question is, is
there
> > any way to turn this off? Servlet API does not provide a way to examine
the
> > headers in a Response, and beisdes, WebSphere could be doing this after
> > service() exits.
>
> We never found any way to enable caching to work with javax Cookies, even
after
> talking to JRun tech support. It's possible that you may be able to do it
in
> WebSphere. Since we couldn't do it through the servlet, we ended up
setting the
> cookie with Javascript in the web page as I mentioned.
>
> As a final thought, here's what Sun's API Javadoc
> (http://java.sun.com/products/servlet/2.2/javadoc/index.html) says about
cookies
> and caching:
> "Cookies affect the caching of the Web pages that use them. HTTP 1.0 does
not
> cache pages that use cookies created with this class. This class does not
> support the cache control defined with HTTP 1.1."
>
> K Mukhar
>
>
___________________________________________________________________________
> 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
___________________________________________________________________________
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
