Search squid archive

Re: Invalid Response

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Henrik Nordstrom <henrik@xxxxxxxxxxxxxxxxxxx>:

> On fre, 2007-11-09 at 16:25 +0100, apmailist@xxxxxxx wrote:
>
> > I encounter An "invalid Response" on a particular site.
>
> What is said in cache.log?

Cache.log doesn't say much on normal debug settings.
With debug on , it says
2007/11/05 15:02:53| parseHttpRequest: end = {}
2007/11/05 15:02:53| parseHttpRequest: prefix_sz = 585, req_line_sz = 121
2007/11/05 15:02:53| clientSetKeepaliveFlag: http_ver = 1.1
2007/11/05 15:02:53| clientSetKeepaliveFlag: method = GET
2007/11/05 15:02:53| The request GET
http://somesite.com/nms/jsp/webForm.jsp?fo=bl&id=S7Nn6isL2ABgb1B35boKb4Z2SiMGMFGb/VEkJUIAIA
is ALLOWED, because it matched 'group_internet'
2007/11/05 15:02:53| clientProcessRequest2: storeGet() MISS
2007/11/05 15:02:53| httpStart: "GET
http://somesite.com/nms/jsp/webForm.jsp?fo=bl&id=S7Nn6isL2ABgb1B35boKb4Z2SiMGMFGb/VEkJUIAIA";
2007/11/05 15:02:53| ctx: enter level 16:
'http://somesite.com/nms/jsp/webForm.jsp?fo=bl&id=S7Nn6isL2ABgb1B35boKb4Z2SiMGMFGb/VEkJUIAIA'
2007/11/05 15:02:53| httpProcessReplyHeader: key
'5C5369ABE7B82C5EC7956CD08C4AFCFC'
2007/11/05 15:02:53| httpProcessReplyHeader: HTTP CODE: 200
2007/11/05 15:02:53| clientBuildReplyHeader: Error, don't keep-alive
2007/11/05 15:02:53| clientSendMoreHeaderData: Appending 1697 bytes after 202
bytes of headers
2007/11/05 15:02:53| The reply for GET
http://somesite.com/nms/jsp/webForm.jsp?fo=bl&id=S7Nn6isL2GABgb1B35boKb4Z2SiMGMFGb/VEkJUIAIA
is ALLOWED, because it matched 'all'
2007/11/05 15:02:53| connStateFree: FD 31
2007/11/05 15:02:53| httpRequestFree:
http://somesite.com/nms/jsp/webForm.jsp?fo=bl&id=S7Nn6isL2ABgb1B35boKb4Z2SiMGMFGb/VEkJUIAIA
2007/11/05 15:02:53| parseHttpRequest: req_hdr = {Host: somesite.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9)
Gecko/20071025 Firefox/2.0.0.9
Accept: image/png,*/*;q=0.5
Accept-Language: en,en-us;q=0.7,fr-fr;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Proxy-Connection: keep-alive
Proxy-Authorization: Basic xxxxxxxxxxxxx




Access.log with log_mime_headers on says :
[HTTP/1.0 502 Bad Gateway\r\nServer: squid\r\nDate: Mon, 05 Nov 2007 15:54:00
GMT\r\nContent-Type: text/html\r\nContent-Length: 1740\r\nExpires: Mon, 05 Nov
2007 15:54:00 GMT\r\nX-Squid-Error: ERR_INVALID_RESP 0\r\n\r]

>
> > Two tcpdumps, one from the squid server, another one from another internet
> > access point, show strange characters just between the headers and the html
> > stanza. See the "5ea" , then the "1" , and the "0".
>
> The interesting dump is the one between Squid and the requested server.
> Not interesting in seeing a dump of a direct request not using Squid.
>
> As already said those numbers is chunked encoding. Nothing to worry
> about, only seen because you bypassed Squid in this request.
>
> Any yes, Squid-2.6 do handle being thrown chunked encoding even if specs
> do not allow servers to respond with chunked encoding. But some release
> was a little buggy and still barfed.. don't remember exact but it was
> quite a while ago (a year or so..).

We're using 2.6ST 16. Could the workaround be buggy in this version ?

>
> And yes, Squid do downgrade HTTP/1.1 requests to HTTP/1.0 as it's not
> yet HTTP/1.1 compliant.
>



> Regards
> Henrik
>


Thanks,

Andrew

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux