Re: [squid-users] Accelerating proxy not matching cgi files

2011/8/25 Amos Jeffries <squid3_at_treenet.co.nz>:
> On 26/08/11 01:59, Mateusz Buc wrote:
>>
>> Ok, I've quite figured it out. The solution was to add 'ignore-cc' to
>> http_port option. Right now I'm getting TCP_IMS_HIT/304 statuses with
>> gen.cgi requests.
>
> Very suspicious if ignoring client-sent Cache-Control: header fixes things.
> What does the client sent Cache-Control header contains?

Now I reconfigured squid to production servers (changed IP + hostname
and added 'login=pass' to cache_peer line). Though it worked well
without authentication on two different servers (there were
TCP_MEM_HIT/200 and TCP_IMS_HIT/304 responses) , on this particular
one it doesn't. Apache configuration + application is the same on
every server. Is squid capable of caching content which requires
'basic' authentication?

At the moment, client Cache-Control says: "Cache-Control: max-age=0 "
and it doesn't send any 'If-Modified-Since" headers. Strange thing is
that it happens only to gen.cgi. index.cgi, however, gets TCP_MISS/304
and there are IMS headers.

My configuration remained the same, except from changes I mentioned
few lines earlier.

Gen.cgi sends "Last-modified: " with the current date plus
"Cache-Control: max-age=3600, s-max-age=7200", but NO
"must-revalidate", since the goal was to reduce amount of queries to
server, so I assume when query is repeated within the max-age period,
it doesn't need to be sent to the server, so "Last-modified:" will be
the same?

Right now I am pretty stuck with this... Any help would be appreciated.

Best regards,
Mateusz Buc

-- 
[ Mateusz 'Blaster' Buc :: blaster@grex.org :: http://blast3r.info ]
[ There's no place like 127.0.0.1. :: +48 724676983 :: GG: 2937287 ]