RE: [squid-users] Reverse proxy caching behaviour with Servlets

hi,

I noticed that the servlet page has response.setContentLength(size) set.
When I removed this line the page was cached.

Any ideas on why this should not be set in the response headers.????

Anuradha

-----Original Message-----
From: Anuradha Hegde [mailto:anuradha@onyx-systems.com]
Sent: Wednesday, July 24, 2002 8:28 AM
To: squid-users@squid-cache.org
Subject: [squid-users] Reverse proxy caching behaviour with Servlets

Hi

I am using Squid 2.4 on Tru64 Unix. It has been configured for Reverse Proxy
caching.
I am trying to use it to be able to cache Servlets being hosted by a Tomcat
implementation.
I find only some of the servlets being cached and am not able to identify
the reason behind this. All the servlets have similar response headers
(which contains Cache-Control, max-age, Expires). The servlets which are not
cached have a more complex page layout.

What could be causing this behaviour? What are the reasons that a Servlet
will not be cached?

Here is the configuration change that I made in the squid.conf file

http_port 8902
httpd_accel_port 10.10.10.10
httpd_accel_port 8902
httpd_accel_single_host_on
httpd_accel_with_proxy_off
httpd_accel_uses_host_header_off
acl acceleratedHost dst 10.10.10.10/255.255.255.255
acl acceleratedPort port 8902
http_access allow acceleratedHost acceleratedPort

Thanks

Anu
Received on Thu Jul 25 2002 - 16:42:20 MDT