On 18.10.2012 04:18, Jakob Curdes wrote:
Hello, we are trying to reverse-proxy a WebDAV-based application in a
split-DNS setup. The application seems to work; however we see error
messages in the cache log like (data partly altered)
GET /whatever/ HTTP/1.0
Accept: */*
Referer: https://whatever.mydomain.com/
Accept-Language: de
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR
3.0.04506.30; .NET4.0C; .NET4.0E; .NET CLR 3.0.4506.2152; .NET CLR
3.5.30729)
Accept-Encoding: gzip, deflate
Host: whatever.mydomain.com
Cookie:
__utma=242084580.446845177.1308037854.13080236854.1308096854.1
Authorization: Basic c2xHRfT0cHN5bTR6b21pY3Jvbi4wMA==
Cache-Control: max-age=259200
Connection: keep-alive
Front-End-Https: On
2012/10/17 16:54:38| httpSendComplete: FD 15: size 562: errflag 0.
2012/10/17 16:54:38| httpReadReply: FD 15: len -1.
2012/10/17 16:54:38| httpReadReply: FD 15: read failure: (11)
Resource temporarily unavailable.
2012/10/17 16:54:38| httpReadReply: FD 15: len -1.
2012/10/17 16:54:38| httpReadReply: FD 15: read failure: (11)
Resource temporarily unavailable.
2012/10/17 16:54:38| httpReadReply: FD 15: len 13343.
I suppose this is the reply to the forwarded request? If so, what
should this message tell me?
The socket on FD 15 disappeared. Look elsewhere in the log for "FD 15"
and it will tell you what connection was setup on that FD and what it
was requesting/responding.
You Squid version would also be helpful. 3.2 series can dump out all
the HTTP header and TCP connection details in a useful form at
debug_options 11,2.
Amos
