On Tue, 14 Jun 2011 10:43:17 +0200, Gontzal wrote:
Hi everybody!!
I get these messages on cache.log:
2011/06/14 10:23:54| clientParseRequestMethod: Unsupported method
attempted by client_ip: This is not a bug. see squid.conf
extension_methods
2011/06/14 10:23:54| clientParseRequestMethod: Unsupported method in
request 'X-Dropbox-Locale: es____'
This 'X-Dropbox-Locale:' is the method being mentioned. Look strange to
you? Squid thinks so.
I guess the requesting software is adding "\nX-Dropbox-Locale: " when
it should be adding "X-Dropbox-Locale: ...\n".
2011/06/14 10:23:54| clientProcessRequest: Invalid Request
when accessing dropbox:
client_ip - user_name [14/Jun/2011:10:23:54 +0200] "GET
http://notify3.dropbox.com/subscribe? HTTP/1.1" 200 366
TCP_MISS:DEFAULT_PARENT
This is one of the other requests. Which succeeded. It might be the
real one which that header was supposed to be attached to. But it is not
easy to be sure since this is already finished. Does not matter anyway,
the problem is in the agent code adding that custom X- header.
doing a tcpdump on squid eth and filtering by client ip address I
obtain this:
10:23:54.184989 IP (tos 0x0, ttl 64, id 25600, offset 0, flags [DF],
proto TCP (6), length 406)
proxy-ip.3128 > client_ip.2712: Flags [P.], cksum 0xe043
(incorrect -> 0x3668), seq 1:367, ack 308, win 6432, length 366
10:23:54.188327 IP (tos 0x0, ttl 128, id 59315, offset 0, flags [DF],
proto TCP (6), length 347)
NP: this type of packet trace is useless for finding out what is inside
the packets. (366 bytes of what?)
I don't understand why it says unsupported method when it is just a
GET. Can anyone help me?
see above.
You can contact the software devs and get them to fix that header.
And/or ignore it and continue. Squid will react by dropping the TCP
links this occurs on. This will only be a user-noticable problem when
pipiline_prefetch is turned on.
HTH
Amos
