Wennie V. Lagmay wrote:
Yes but I don't know how to start solving it. To start with I am looking for extension_method but unfortunately there is no example on howto, I am also trying google it with with no luck. Can you please guide me on how to solve this one.
thanks
The unknown binary chars at the start of the method mean
extension_methods will not be much help.
Locate one of the IPs which seems fairly regular. Contact that client
and talk about whats going on. Do they actually use GoogleTalk or is
this some broken malware?
There has been report of some infection recently which constantly
contacts google. This may be it. Or they may have configured the proxy
as a SOCKS proxy.
A trace of the traffic flow going into Squid will likely show what two
binary characters are being prepended to the request. Maybe contacting
someone at Google to report the bug in their software.
When you figure out exactly what is going on for one, that should help
with the rest. And please report back here so others with the same
problem can get better help.
Good luck.
Amos
----- Original Message -----
From: "Amos Jeffries" <squid3@xxxxxxxxxxxxx>
To: "Wennie V. Lagmay" <wlagmay@xxxxxxxxxxxxx>
Cc: "squid-users" <squid-users@xxxxxxxxxxxxxxx>
Sent: Saturday, January 17, 2009 4:13:54 PM (GMT+0300) Asia/Kuwait
Subject: Re: request for help
Wennie V. Lagmay wrote:
Hi Amos,
Also I am having the following error message:
Have you read these carefully?
Web application: Google Talk
Client IPs: several as listed in the messages
Problem:
Sending broken HTTP requests: <binary><binary>CONNECT instead of CONNECT.
2009/01/17 15:53:36| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:53:36| clientProcessRequest: Invalid Request
2009/01/17 15:53:48| statusIfComplete: Request not yet fully sent "POST http://www.google.com/m/appr eq/mobilevideo"
2009/01/17 15:53:57| clientParseRequestMethod: Unsupported method attempted by 192.168.72.42: This i s not a bug. see squid.conf extension_methods
2009/01/17 15:53:57| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:53:57| clientProcessRequest: Invalid Request
2009/01/17 15:54:07| clientParseRequestMethod: Unsupported method attempted by 192.168.16.193: This is not a bug. see squid.conf extension_methods
2009/01/17 15:54:07| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:54:07| clientProcessRequest: Invalid Request
2009/01/17 15:54:14| clientParseRequestMethod: Unsupported method attempted by 192.168.92.24: This i s not a bug. see squid.conf extension_methods
2009/01/17 15:54:14| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:54:14| clientProcessRequest: Invalid Request
2009/01/17 15:54:17| clientParseRequestMethod: Unsupported method attempted by 192.168.29.196: This is not a bug. see squid.conf extension_methods
2009/01/17 15:54:17| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:54:17| clientProcessRequest: Invalid Request
2009/01/17 15:54:22| clientParseRequestMethod: Unsupported method attempted by 192.168.11.138: This is not a bug. see squid.conf extension_methods
2009/01/17 15:54:22| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:54:22| clientProcessRequest: Invalid Request
2009/01/17 15:54:23| ctx: enter level 0: 'http://msgr.updates.yahoo.com/vitality_proxy/V1/getEvents ?max=10&alias=sharmila.saji&fmt=2.0&intl=us&os=win&ver=9.0.0.2034&buddies=(ignatiusgeorge_2007)'
2009/01/17 15:54:23| http.cc(561) HttpStateData::cacheableReply: unexpected http status code 0
2009/01/17 15:54:43| ctx: exit level 0
2009/01/17 15:54:43| clientParseRequestMethod: Unsupported method attempted by 192.168.121.150: This is not a bug. see squid.conf extension_methods
2009/01/17 15:54:43| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:54:43| clientProcessRequest: Invalid Request
2009/01/17 15:54:57| clientParseRequestMethod: Unsupported method attempted by 192.168.29.235: This is not a bug. see squid.conf extension_methods
2009/01/17 15:54:57| clientParseRequestMethod: Unsupported method in request '__CONNECT www.google.c om:443 HTTP/1.0__User-Agent: Google Talk__Host: www.google.com__Content-Length'
2009/01/17 15:54:57| clientProcessRequest: Invalid Request
regards,
wennie
----- Original Message -----
From: "Wennie V. Lagmay" <wlagmay@xxxxxxxxxxxxx>
To: "Amos Jeffries" <squid3@xxxxxxxxxxxxx>
Cc: "squid-users" <squid-users@xxxxxxxxxxxxxxx>
Sent: Saturday, January 17, 2009 4:27:34 PM (GMT+0300) Asia/Kuwait
Subject: Re: request for help
Hi Amos,
Since we a have numbers of subscribers It is hard for me to identify and visit each subscriber. You see I have another proxy running on version squid-2.6 Stable 3 and we not facing any problem.
Do you have any idea how can I solve it on the squid level instead of identifying the clients, and how am I going to fix it. Can you recommend installing the older version 2.6 stable 3 instead?
Thanks a lot
----- Original Message -----
From: "Amos Jeffries" <squid3@xxxxxxxxxxxxx>
To: "Wennie V. Lagmay" <wlagmay@xxxxxxxxxxxxx>
Cc: "squid-users" <squid-users@xxxxxxxxxxxxxxx>
Sent: Saturday, January 17, 2009 2:01:19 PM (GMT+0300) Asia/Kuwait
Subject: Re: request for help
Wennie V. Lagmay wrote:
I installed squid-3.0 STABLE11 and at first it is working smooth, but after 1 day the proxy is working very very slow and dying, I am getting an error similar below. Can anybody help me on my problem please.
2009/01/16 22:42:47| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/16 22:42:50| tunnelReadServer: FD 3918: read failure: (0) Success
2009/01/16 22:42:51| tunnelReadServer: FD 3767: read failure: (0) Success
Thanks in advance,
Wennie
One of the client apps (looks like something a custom built app does
rather than a browser) using your proxy is sending garbage in the HTTP
headers.
You need to track down if you can which client is doing this and fix it.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE5 or 3.0.STABLE11
Current Beta Squid 3.1.0.3
