Farhad Ibragimov wrote:
Hi experts How can i solve this ? clientProcessRequest: Invalid Request 2009/07/27 20:36:35| clientParseRequestMethod: Unsupported method attempted by 85.132.32.50: This is not a bug. see squid.conf extension_methods 2009/07/27 20:36:35| clientParseRequestMethod: Unsupported method in request '_' 2009/07/27 20:36:35| clientProcessRequest: Invalid Request 2009/07/27 20:36:36| clientParseRequestMethod: Unsupported method attempted by 85.132.32.50: This is not a bug. see squid.conf extension_methods 2009/07/27 20:36:36| clientParseRequestMethod: Unsupported method in request '_' 2009/07/27 20:36:36| clientProcessRequest: Invalid Request 2009/07/27 20:36:37| clientParseRequestMethod: Unsupported method attempted by 85.132.32.50: This is not a bug. see squid.conf extension_methods 2009/07/27 20:36:37| clientParseRequestMethod: Unsupported method in request '_' 2009/07/27 20:36:37| clientProcessRequest: Invalid Request 2009/07/27 20:36:43| clientParseRequestMethod: Unsupported method attempted by 85.132.32.50: This is not a bug. see squid.conf extension_methods 2009/07/27 20:36:43| clientParseRequestMethod: Unsupported method in request '_' 2009/07/27 20:36:43| clientProcessRequest: Invalid Request 2009/07/27 20:36:44| clientParseRequestMethod: Unsupported method attempted by 85.132.32.50: This is not a bug. see squid.conf extension_methods 2009/07/27 20:36:44| clientParseRequestMethod: Unsupported method in request '_BitTorrent protocol' 2009/07/27 20:36:44| clientProcessRequest: Invalid Request
With the information given, the only solution I can provide is identify the non-HTTP traffic originating from 85.132.32.50, and prevent it from reaching your Squid cache.
Chris
