Thanks. Is there a way that I can override this behavior and revert back to the old behavior? I'm guessing that you're using a HTTP header to do this? I'm guessing that I can use HttpServletResponse.setHeader() to override it? Is it the "expires" header, or something else? What value is it setting now, and what was the original value?
Jon ----- Original Message ----- From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]>; "Jonathan Eric Miller" <[EMAIL PROTECTED]> Sent: Thursday, February 14, 2002 6:26 PM Subject: Re: Did the default HTTP expires header change in Tomcat? > > Yeah, I just tried my application in 4.0.1 and it doesn't expire. > Something > > seems to have changed in 4.0.2. > > Yes, the content which is protected through a security constraint is marked > as non cacheable (which fixes a security problem where a proxy would cache > the pages). > > Remy > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
