On 20/01/11 00:33, diginger wrote:
Hi I have updated my squid version 3.0 STABLE25. But its caching for the bad response i.e. TCP_NEGATIVE_HIT/204 or TCP_NEGATIVE_HIT/400 but not caching for sttaus code 200 i.e.TCP_MISS/200. Following http://wiki.squid-cache.org/ConfigExamples/Reverse/BasicAccelerator online guide I have done the following configuration #These two lines are on top of config file http_port 80 accel defaultsite=<mysite DNS>:8081
It's generally problematic to change ports in transit. The backend application needs support and maybe extra configuration to be aware that the client is using port 80.
You will likely need: http_port 80 accel vport=8081 defaultsite=$public_domain http_poort 8081 accel defaultsite=$public_domain or http_port 80 accel vhost vport=8081 defaultsite=$public_domain http_poort 8081 accel vhost defaultsite=$public_domain
cache_peer 192.234.172.25 parent 8081 0 no-query originserver name=myAccel # And finally deny all other access to this proxy #http_access allow localhost #http_access deny all http_access allow our_sites cache_peer_access myAccel allow our_sites cache_peer_access myAccel deny all Do squid need to be configured diffrently for diffrent content type? I have application/json set as header content type as I am expevtin JSON response. Pease guide, thanks in advance.
Please supply your full config file (without the comment lines). There are many things which *might* be affecting this problem.
Also did you read the reference pages in my reply from yesterday? Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.10 Beta testers wanted for 3.2.0.4