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
