-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pid,
On 7/14/2011 6:37 AM, Pid wrote: > I'd ask the OP to back that up with an explanation and some proof, > contrary to the below: Can you clarify this? It looks like request and response headers jumbled together. > Request URL:http://localhost:8081/tomcat.png Request Method:GET > Status Code:304 Not Modified ^^^ Looks like start of response. > Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 > > Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 > Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 > Cache-Control:max-age=0 Connection:keep-alive Host:localhost:8081 > If-Modified-Since:Sat, 02 Jul 2011 21:38:58 GMT > If-None-Match:W/"5103-1309642738000" User-Agent:Mozilla/5.0 > (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1 (KHTML, like > Gecko) Chrome/14.0.803.0 Safari/535.1 ^^^ Definitely client headers. > Date:Thu, 14 Jul 2011 10:35:31 GMT ETag:W/"5103-1309642738000" > Server:Apache-Coyote/1.1 ^^^ Definitely response headers. Neither Expires nor Last-Modified nor Cache-Control appear in the response headers, which was the original complaint. One could argue that Etag is a proxy/replacement for Expires and Last-Modified. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4e/fsACgkQ9CaO5/Lv0PD+ogCdEaesU28FzNXO2EIvrc6PnHYk Ly0AnAgOuc5FijuNHjgiwMZ+M6r/g4wb =LeW+ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
