Sorry, I don't know enough about mod_expires to say anything about this logs. So I can't help you with that.
P.S.: You are serving static pages from tomcat ? I wouldn't recommend that. If there are links on the pages you depend on cookies for session managment. Even if there is no functional need for session management, it should be used, if there are links on the static pages. Otherwise each link will open a new session if the user disabled cookies. Said that, there is an alternate solution to your problem: Create a filter that sets the expire header. > -----Urspr�ngliche Nachricht----- > Von: Michele Milani [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 11. Dezember 2001 11:45 > An: 'Tomcat Users List' > Betreff: RE: Apache + mod_jk (ajp13) + Tomcat: no "Expires" header in > the response <snip/> > This only works for HTML code generated by the servlet, not > for static HTML > pages that reside under $TOMCAT_HOME/webapps/test. > Anyway, in both cases, Apache returns always the same date! > And it not the > creation/modification date/time of any file under > $TOMCAT_HOME/webapps/test... can it be Tomcat startup time? <snip/> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
