ons 2006-02-15 klockan 19:08 +0100 skrev Maciej Zięba: > * Here are a couple of last lines from cache.log > > 2006/02/15 13:52:02| WARNING: Forwarding loop detected for: > Client: 127.0.0.1 http_port: 127.0.0.1:80 > REPORT http://xxx:81/svn/SwordFish/Trunk/SwordFish/SwordSite HTTP/1.0 > Host: xxx > User-Agent: SVN/1.2.1 (r15230) neon/0.24.7 > Content-Length: 109 > Content-Type: text/xml > Accept-Encoding: gzip > Accept-Encoding: gzip > Via: 1.1 xxx:80 (squid/2.5.STABLE11) > X-Forwarded-For: 127.0.0.1 > Cache-Control: max-age=259200 > Connection: keep-alive > The above is the key to this mystery. The request got denied because your Squid was talking to itself and obviously something had gone wrong. Now the question to ask is why did Squid talk to itself on this request? any cache_peer lines in your squid.conf? What port are Squid running on? Can you please switch back to the native access.log format. This provides more useable information in diagnosing problems like this.. It is NOT an access control problem even if it may look so from the erro code returned. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
