Re: [squid-users] forward loop

Hi Mustafa,

Can you please post your squid.conf ? (Remove all comments and passwords
etc)

Cheers,

Pieter

On 2/02/2012 23:04, Mustafa Raji wrote:
> hi
> please i have a forward loop warning in my cache.log what is the cause of it
> i check the internet and find the cause is using peer squid configuration and the two cache server has the same visible_hostname but i never used the peer in my configuration i have one cache server with intercept configuration please can you tell me what is causes to the cache forward loop the warning message is from cache.log
>
> 2012/02/02 12:02:23| WARNING: Forwarding loop detected for:
> POST /2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bnpuss,ConnType=KeepAlive HTTP/1.1
> Accept: */*
> Content-Type: application/octet-stream
> User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Win32)
> UserAgent: blugro2relay.groove.microsoft.com
> Content-Length: 22
> Pragma: no-cache
> Expires: 0
> Host: 192.168.40.2:3128
> Via: 1.0 squidtest (squid/3.1.11), 1.1 squidtest (squid/3.1.11), 1.1 squidtest (squid/3.1.11)
> X-Forwarded-For: 192.168.40.1, 192.168.40.2, 192.168.40.2
> Cache-Control: no-cache, max-age=0
> Connection: keep-alive
>
> and this error continues to appear with increasing the values of via and x-forward-for
> my access.log file show this information at the same time of the loop
> the ip 192.168.40.2 is the CacheServer ip
>
> Thu Feb 2 12:02:23 2012 0 192.168.40.1 TCP_IMS_HIT/304 287 GET http://crl.microsoft.com/pki/crl/products/WinPCA.crl - NONE/- application/pkix-crl
> Thu Feb 2 12:02:24 2012 898 192.168.40.1 TCP_MISS/400 237 POST http://65.55.122.232/ - DIRECT/65.55.122.232 -
> Thu Feb 2 12:02:24 2012 8 192.168.40.2 NONE/400 69168 NONE error:request-too-large - NONE/- text/html
> Thu Feb 2 12:02:24 2012 19 192.168.40.2 TCP_MISS/400 69275 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 23 192.168.40.2 TCP_MISS/400 69377 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 26 192.168.40.2 TCP_MISS/400 69479 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 30 192.168.40.2 TCP_MISS/400 69581 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 34 192.168.40.2 TCP_MISS/400 69683 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 37 192.168.40.2 TCP_MISS/400 69785 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 41 192.168.40.2 TCP_MISS/400 69887 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 44 192.168.40.2 TCP_MISS/400 69989 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 48 192.168.40.2 TCP_MISS/400 70091 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 51 192.168.40.2 TCP_MISS/400 70193 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 55 192.168.40.2 TCP_MISS/400 70295 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
> Thu Feb 2 12:02:24 2012 58 192.168.40.2 TCP_MISS/400 70397 POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/n7hngumkwg46fvvc2zuwzzcd6y43i3da4bn$
>
>
>
> after that this status appear to me in cache.log
>
> 2012/02/02 12:02:33| statusIfComplete: Request not yet fully sent "POST http://192.168.40.2:3128/2.0/blugro2relay.groove.microsoft.com/3m4dy9mseq7e9h39xecabcaqj24zjcgw4zts55s,ConnType=LongLived"
>
> and in 12:02:35 the server is return to work normally
>
> please can you help me in finding what is the cause of this warning
Received on Thu Feb 02 2012 - 10:08:40 MST