[squid-users] Zero Sized Reply
Jorgeley Junior
jorgeley at gmail.com
Thu Aug 27 18:13:59 UTC 2015
seens like the web server is a ISS, look at that:
2015/08/27 11:44:11.087 kid1| ctx: enter level 0: '
http://www.grupoatuall.com.br/favicon.ico'
2015/08/27 11:44:11.087 kid1| http.cc(695) processReplyHeader:
processReplyHeader: key 'B8D92AE82DF4B8ED3202042600CED02D'
2015/08/27 11:44:11.087 kid1| HttpHeader.cc(446) HttpHeader: init-ing hdr:
0x20b0218 owner: 3
2015/08/27 11:44:11.087 kid1| cbdata.cc(299) cbdataInternalAlloc:
Allocating 0x20ada98
2015/08/27 11:44:11.087 kid1| HttpHeader.cc(1192) has: 0x20b0218 lookup for
49
2015/08/27 11:44:11.087 kid1| HttpHeader.cc(1192) has: 0x20b0218 lookup for
11
2015/08/27 11:44:11.087 kid1| HttpHeader.cc(1192) has: 0x20b0218 lookup for
26
2015/08/27 11:44:11.087 kid1| HttpHeader.cc(595) parse: parsing hdr:
(0x20b0218)
Content-Type: text/html^M
Server: Microsoft-IIS/7.5^M
X-Powered-By: ASP.NET^M
X-Powered-By-Plesk: PleskWin^M
Date: Thu, 27 Aug 2015 14:48:18 GMT^M
Content-Length: 1080^M
...(more logs)
2015/08/27 11:44:11.087 kid1| HttpMsg.cc(176) parse: HttpMsg::parse success
(190 bytes) near 'HTTP/1.1 404 Not Found^M
Content-Type: text/html^M
Server: Microsoft-IIS/7.5^M
X-Powered-By: ASP.NET^M
X-Powered-By-Plesk: PleskWin^M
Date: Thu, 27 Aug 2015 14:48:18 GMT^M
Content-Length: 1080^M
^M
<HTML>^M
<HEAD>^M
<TITLE>404 Not Found</TITLE>^M
</HEAD>^M
<BODY>^M
<H1>Not Found</H1>^M
The requested document was not found on this server.^M
<P>^M
<HR>^M
<ADDRESS>^M
Web Server at
grupoatuall.com.br^M
</ADDRESS>^M
</BODY>^M
</HTML>^M
^M
<!--^M
- Unfortunately, Microsoft has added a clever new^M
- "feature" to Internet Explorer. If the text of^M
- an error's message is "too small", specifically^M
- less than 512 bytes, Internet Explorer returns^M
- its own error message. You can turn that off,^M
- but it's pretty tricky to find switch called^M
- "smart error messages". That means, of course,^M
- that short error messages are censored by default.^M
- IIS always returns error messages that are long^M
- enough to make Internet Explorer happy. The^M
- workaround is pretty simple: pad the error^M
- message with a big comment like this to push it^M
- over the five hundred and twelve bytes minimum.^M
- Of course, that's exactly what you're reading^M
- right now.^M
-->^M
'
2015/08/27 11:44:11.087 kid1| http.cc(739) processReplyHeader: HTTP Server
local=192.168.25.2:43147 remote=200.98.190.9:80 FD 98 flags=1
2015/08/27 11:44:11.087 kid1| http.cc(740) processReplyHeader: HTTP Server
REPLY:
---------
HTTP/1.1 404 Not Found^M
572544,4 69%
2015-08-27 14:49 GMT-03:00 Jorgeley Junior <jorgeley at gmail.com>:
> Amos, thank you so much for attention, but sorry, I didn't understand what
> you said.
> So, I tried to change the http for https and it showed the website and i
> added the security exception for no trusted certificate, but I really would
> like that the squid didn't show the error.
> Why http show de Zero Sized Reply and https no?
>
> 2015-08-27 14:21 GMT-03:00 Amos Jeffries <squid3 at treenet.co.nz>:
>
>> On 28/08/2015 5:04 a.m., Jorgeley Junior wrote:
>> > more logs:
>>
>> Aha! the first bit. What Squid sent to the server:
>>
>> > 2015/08/27 11:43:31.301 kid1| http.cc(2217) sendRequest: HTTP Server
>> local=
>> > 192.168.25.2:43127 remote=200.98.190.9:80 FD 66 flags=1
>> > 2015/08/27 11:43:31.301 kid1| http.cc(2218) sendRequest: HTTP Server
>> > REQUEST:
>> > ---------
>> > GET / HTTP/1.1^M
>> > Host: www.grupoatuall.com.br^M
>> > User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0)
>> Gecko/20100101
>> > Firefox/40.0^M
>> > Accept:
>> text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8^M
>> > Accept-Language: pt-BR,pt;q=0.8,en-US;q=0.5,en;q=0.3^M
>> > Accept-Encoding: gzip, deflate^M
>> > Via: 1.1 firewall (squid)^M
>> > X-Forwarded-For: 192.168.1.11^M
>> > Cache-Control: max-age=259200^M
>> >
>>
>>
>> Now. Notice the FD number (66) on the line at the top there. And look
>> for the very next set of headers with matching set of local=,remote=,FD
>> values but titled "HTTP Server RESPONSE".
>>
>> That is apparently the reply that failed.
>>
>> * Compare the timestamps of the request/reply lines to see if it reminds
>> you of any kind of timeout value you are aware of. Multiples of 30sec or
>> 5min are common for timeout settings.
>>
>> * anything visibly wrong about the reply headers?
>>
>> Amos
>>
>
>
>
> --
>
>
>
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150827/b52c73cc/attachment.html>
More information about the squid-users
mailing list