Costin Manolache wrote:
Bill Barker wrote:
At the moment (with the default settings), Tomcat 4.1.x and higher add
HTTP headers to non-SSL protected pages to prevent intermediate proxies
from
caching them. According to the HTTP/1.1 RFC (and even the HTTP/1.0 RFC),
POSTed pages are not allowed to
Remy Maucherat wrote:
Bill Barker wrote:
I'm saying to *not* include the headers, because any compliant proxy will
not cache anyway. At the moment, SSL connections do not set the headers
(since they also can't be cached), and that is the only current
exception.
At the moment, hitting the "back"
Bill Barker wrote:
I'm saying to *not* include the headers, because any compliant proxy will
not cache anyway. At the moment, SSL connections do not set the headers
(since they also can't be cached), and that is the only current exception.
At the moment, hitting the "back" button in the browser to
- Original Message -
From: "Costin Manolache" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 16, 2003 8:38 PM
Subject: Re: [PROPOSAL] Add Post to the clear list for protected pages
> Bill Barker wrote:
>
> > At the moment (with the d
Bill Barker wrote:
> At the moment (with the default settings), Tomcat 4.1.x and higher add
> HTTP headers to non-SSL protected pages to prevent intermediate proxies
> from
> caching them. According to the HTTP/1.1 RFC (and even the HTTP/1.0 RFC),
> POSTed pages are not allowed to be cached by pr
At the moment (with the default settings), Tomcat 4.1.x and higher add HTTP
headers to non-SSL protected pages to prevent intermediate proxies from
caching them. According to the HTTP/1.1 RFC (and even the HTTP/1.0 RFC),
POSTed pages are not allowed to be cached by proxies (for the obvious
reasons
