I do set some values to prevent caching.
response.setHeader("Pragma", "no-cache");
response.setHeader("Expires", "0");
response.setHeader("Cache-control", "no-cache, must-revalidate");
I'll didn't really implement caching in the way you think. I just cache the Template object from loading my XSLT. I don't actually cache the result. I apply that template for every request (if my servlet gets called by the container!)
I do want to move to Cocoon, but that won't happen for several months (at least not for the main app).
Thanks,
David
Shapira, Yoav wrote:
Howdy,
So, before I spend a bunch of time pouring over the source, can someoneWhat caching the web server is and isn't allowed to do is fairly well
tell me if tomcat 4 (or the HttpConnector) looks at the incomming URL
and gives a cached result if the URL hasn't changed? I am using mod_jk
with apache, but that hasn't changed since when I used tomcat 3.x. (nor
has my apache version or config changed).
Any ideas?
defined in the HTTP protocol specification: RFC 2616. By the way, the
still experimental RFC 2295 is fairly interesting in this area. You can
also check out the JavaDoc for methods like
HttpServlet.getLastModified(HttpServletRequest req). You can override
this method in your servlet if necessary.
Alternatively, as the HTTP specifications detail, you can use various
response headers to indicate the response shouldn't be cached. A google
search on no-cache HTTP headers will give a ton of information on this
subject.
You probably want to do the above anyways to avoid a proprietary
solution to caching pages like you have used in the past.
Yoav Shapira
Millennium ChemInformatics
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
