request caching?

[David Kavanagh <da...@dotech.com>]

I've been using tomcat since 3.2.1 and use XSLT to take my servlet 
output and turn it into HTML.
I wrote code to check the XSLT file modification date and auto-reload it 
if the file had been modified. So, in the browser, I could just hit 
reload and get updated XSLT. This is great for debugging and I would 
typicaly disable it with a property for production.
My problem (and question) is about what happened when I moved to tomcat 
4. We started using 4.0.4-le-jdk14 many months ago and I noticed that my 
auto reload doesn't work like before. My log says my XSLT was reloaded, 
but I don't see it in the browser unless I change the URL slightly. I 
can add a parameter and then I see the updated XSLT output.
So, before I spend a bunch of time pouring over the source, can someone 
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?

David


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>