-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Something like self-made bullshit proto,
something like bittorrent-over-http or something. Heh.
Webmasters still respect us!
12.08.2016 22:00, Amos Jeffries пишет:
> On 13/08/2016 3:17 a.m., joe wrote:
>> 2016/08/12 18:14:51.855 kid1| 74,9| RequestParser.cc(316) parse: Parse
>> buf={length=135,
data='»ß)Nr—»à*Ns—¼à*Os˜¼á+Ot˜½á+Pt™½â,Pu™¾â,Quš¿ä
>> .Rw›Àä
>> .SwœÀå
>> /3W| Åé3X|¡Åê4X}¡Æê4Y}¢Æë5Y~¢Çë5Z~£Çì6Z£Èì6[¤Èí7[€¤Éí7\€¥'}
>> 2016/08/12 18:14:51.856 kid1| 74,5| RequestParser.cc(263)
>> parseRequestFirstLine: parsing possible request: buf.length=135
>> 2016/08/12 18:14:51.856 kid1| 74,9| RequestParser.cc(264)
>> parseRequestFirstLine:
»ß)Nr—»à*Ns—¼à*Os˜¼á+Ot˜½á+Pt™½â,Pu™¾â,Quš¿ä
>> .Rw›Àä
>> .SwœÀå
>> /3W| Åé3X|¡Åê4X}¡Æê4Y}¢Æë5Y~¢Çë5Z~£Çì6Z£Èì6[¤Èí7[€¤Éí7\€¥
>> 2016/08/12 18:14:51.856 kid1| 74,5| RequestParser.cc(339) parse:
>> request-line: retval -1: line={135,
>> data='»ß)Nr—»à*Ns—¼à*Os˜¼á+Ot˜½á+Pt™½â,Pu™¾â,Quš¿ä .Rw›Àä
>> .SwœÀå
>> /3W| Åé3X|¡Åê4X}¡Æê4Y}¢Æë5Y~¢Çë5Z~£Çì6Z£Èì6[¤Èí7[€¤Éí7\€¥'}
>> 2016/08/12 18:14:51.856 kid1| 74,5| RequestParser.cc(340) parse:
>> request-line: method: NONE
>> 2016/08/12 18:14:51.856 kid1| 74,5| RequestParser.cc(341) parse:
>> request-line: url:
>> 2016/08/12 18:14:51.856 kid1| 74,5| RequestParser.cc(342) parse:
>> request-line: proto: NONE/0.0
>> 2016/08/12 18:14:51.856 kid1| 74,5| RequestParser.cc(343) parse: Parser:
>> bytes processed=0
>> 2016/08/12 18:14:51.856 kid1| 11,2| Stream.cc(266)
sendStartOfMessage: HTTP
>> Client local=173.236.187.17:80 remote=10.4.4.61:7937 FD 11 flags=33
>> 2016/08/12 18:14:51.856 kid1| 11,2| Stream.cc(267)
sendStartOfMessage: HTTP
>> Client REPLY:
>> ---------
>> HTTP/1.1 400 Bad Request
>> Server: squid
>> Mime-Version: 1.0
>> Date: Fri, 12 Aug 2016 15:14:51 GMT
>> Content-Type: text/html;charset=utf-8
>> Content-Length: 3367
>> X-Squid-Error: ERR_PROTOCOL_UNKNOWN 0
>> X-Cache: MISS from proxy.netgatesss.com
>> Connection: close
>>
>>
>
> That 400 statuss output is correct. This stream of binary octets does
> not make an HTTP request message, not even close.
>
> The "problem" (if you can call it that) it that some application is
> attempting to pass non-HTTP garbage over the registered HTTP port 80.
> The solution is to stop that application. Squids output is the polite
> way of telling it that it has to use HTTP over that port.
>
> Amos
>
> _______________________________________________
> squid-users mailing list
> squid-users@xxxxxxxxxxxxxxxxxxxxx
> http://lists.squid-cache.org/listinfo/squid-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXrfwHAAoJENNXIZxhPexGTXgH/0ox4ESdUd2Nph3M988WrahP
nRQARZvEfGHXD80eQOseLqSYiTTsC0D2XxDN2qthYqLBd6B19EJ8A+z4+pmHUeYq
NSubVjPC4tEtX0n1F0v4BWxw++vljwCRP8eRvsX7Quccb86LtVtHIJRVkuwe0c78
YEg/TucNmb2UGMawlSpeP4Tejo9LTVysIyl1zCAI21IYiBIl4RUHTo1Fp6GBDhTN
zn1Pf7EwJPjoZYBsgB2jufuHbjRzXs4MyXaagH4tTNwllTkyALdRw8KY4JXgLEUG
7Reh2zoTgA+FCIgCQumgqbe0lfOIirxnhU7owNVOnntLqIzS0uYHT1VzFLyfPT4=
=m+4M
-----END PGP SIGNATURE-----
Attachment:
0x613DEC46.asc
Description: application/pgp-keys
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
