On Saturday 22 October 2005 20:53, Yavor Trapkov wrote: > Good point!, but it doesn't seems to be marked uncachable, here are two > examples > > ------------ > HTTP request sent, awaiting response... > HTTP/1.1 200 OK > Set-Cookie: JSESSIONID=8A211D396681857816C48E62C2E0D8A5; Path=/ > Content-Type: text/html;charset=ISO-8859-1 > Content-Length: 18 > Date: Sat, 22 Oct 2005 19:47:57 GMT > Server: Apache-Coyote/1.1 > Connection: Keep-Alive > Length: 18 [text/html] There's nothing to make that cacheable, and there's the cookie to make it unsuitable for cacheing. > HTTP/1.1 200 OK > ETag: W/"18-1130009410000" > Last-Modified: Sat, 22 Oct 2005 19:30:10 GMT > Content-Type: text/html > Content-Length: 18 > Date: Sat, 22 Oct 2005 19:48:06 GMT > Server: Apache-Coyote/1.1 > Connection: Keep-Alive > Length: 18 [text/html] That should be cacheable with the Last-Modified and ETag, though 18 bytes might seem too little to be worth it. > >> I'm using apache (2.0.54) as a frontend server to proxy content from > >> application servers, Cacheing was never one of 2.0's stronger features. You might want to upgrade to 2.1, or at least use 2.1's mod_cache. My only other suggestion would be to set LogLevel Debug and see if it generates any useful information in the error log. -- Nick Kew --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|