> > my acceess log doesn't gives such an error it only show messgag: > > 441 10.1.21.10 TCP_MISS/400 26687 GET > http://update.microsoft.com/v8/windowsupdate/redir/muv3wuredir.cab? - > DIRECT/65.55.184.253 text/html > > however, cache log gives the following error. > > xxx.xxxxxx.xxx.xx (squid/3.0.STABLE14), 1.0 xxx.xxxxxx.xxx.xx > (squid/3.0.STABLE14), 1.0 xxx.xxxxxx.xxx.xx (squid/3.0.STABLE14), 1.0 > xxx.xxxxxx.xxx.xx (squid/3.0.STABLE14), 1.0 xxx.xxxxxx.xxx.xx > (squid/3.0.STABLE14) > X-Forwarded-For: 10.1.21.10, 192.168.1.93, 192.168.1.93, 192.168.1.93, > 192.168.1.93, 192.168.1.93, 192.168.1.93, 192.168.1.93, 192.168.1.93, > 192.168.1.93, 192.168.1.93, 192.168.1.93, 192.168.1.93, 192.168.1.93, > 192.168.1.93, 192.168.1.93, 192.168.1.93, 192.168.1.93, 192.168.1.93, > 192.168.1.93, 192.168.1.93, 192.168.1.93, 192.168.1.93, Cache-Control: > max-age=259200 > Connection: keep-alive > > there are lot of such message appear in cache.log whenever i initiate a > single request for site yahoo or google etc. What does that look like to you? I see your squid receiving a request and deciding to send it back to itself again. You very urgently need to find out why that is happening and stop it. Common causes are: - transparent interception. Configured to catch _everything_ exiting the LAN, failing to exempt squid box. - peering with a domain named peer. Domain name pointing at multiple IP, including local squid box IP. - multiple interface on the local squid box. Peering with self on other interface. Your squid should by default be detecting such looping and aborting the requests after the second return. You have a secondary issue as to why your squid lets it get longer than "X-Forwarded-For: 10.1.21.10, 192.168.1.93, 192.168.1.93,". Amos > > 2009/05/13 17:43:39| clientProcessRequest: Invalid Request > > --- On Thu, 5/14/09, Matus UHLAR - fantomas <uhlar@xxxxxxxxxxx> wrote: > >> From: Matus UHLAR - fantomas <uhlar@xxxxxxxxxxx> >> Subject: Re: the request or reply is too large squid >> To: squid-users@xxxxxxxxxxxxxxx >> Date: Thursday, May 14, 2009, 1:23 AM >> On 13.05.09 06:47, goody goody >> wrote: >> > Subject: the request or reply is too >> large squid >> >> > I have setup transparent proxy on squid 3.0 stable 14 >> on freebsd 7. but it >> > gives me the subject error. after studying the error >> on net i found >> > suggestions to add followings in squid.conf, but it >> didn't helped me out >> > even. >> > >> > request_header_max_size 10 KB >> > request_body_max_size 1 MB >> > reply_header_max_size 40 KB >> > reply_body_max_size 0 >> > >> > BTW I am using ipfw as local firewall. >> > >> > pls guide me how i can tackle this situation. >> >> one of them is not big enough. Have you checkd access logs >> from the time you >> see this error? >> >> It's probably request_body_max_size too small, when users >> are e.g. uploading >> big files to webmail, they may need much bigger >> request_body. >> >> -- >> Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx >> ; http://www.fantomas.sk/ >> Warning: I wish NOT to receive e-mail advertising to this >> address. >> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek >> reklamnu postu. >> Nothing is fool-proof to a talented fool. >> > > > >
