The first response is not cacheable. It contains no cache validator (Etag, Last-Modified, Expires). The second is cacheable. You must disable cacheing of Set-Cookie using "CacheIgnoreHeaders set-cookies" With LogLevel debug you will get all the traces you need to understand why a response does not get cached. I would not use memory cache with Apache 2.0.54. I used it without problems with Apache 2.0.49, but I ran into core dumps in Apache 2.0.54. Probably does not do you much good anyway. -ascs -----Original Message----- From: Yavor Trapkov [mailto:trapkov@xxxxxxxxxxxx] Sent: Saturday, October 22, 2005 9:54 PM To: users@xxxxxxxxxxxxxxxx Subject: Re: [users@httpd] using cache in reverse proxy mode 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] 21:47:49 (676.08 KB/s) - `index.jsp' saved [18/18] ---------------- HTTP request sent, awaiting response... 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] 21:47:58 (258.50 KB/s) - `index.html' saved [18/18] --------------------------------------------------------------------- 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
|