Landy Landy wrote:
Hello.
How can I avoid these lines:
2010/01/31 19:44:21| clientParseRequestMethod: Unsupported method attempted by
172.16.100.56: This is not a bug. see squid.conf extension_methods
2010/01/31 19:44:21| clientParseRequestMethod: Unsupported method in request
'h3_`___z___Ca_______A_W'f_________8g_8|iF__u~$__"__(_E___)R_h[_[_____p_r4o__?U_w~mn___u____n____9S__'
2010/01/31 19:44:21| clientProcessRequest: Invalid Request
2010/01/31 19:53:01| WARNING: redirector #1 (FD 8) exited
2010/01/31 19:54:03| clientParseRequestMethod: Unsupported method attempted by
172.16.100.56: This is not a bug. see squid.conf extension_methods
2010/01/31 19:54:03| clientParseRequestMethod: Unsupported method in request
'z__y____AfN[___t___h_____W___^_a____V______4_____._______A__qY__}s_[f___w^1_7W_E*_&%e________S`____a'
2010/01/31 19:54:03| clientProcessRequest: Invalid Request
2010/01/31 19:58:41| clientParseRequestMethod: Unsupported method attempted by
172.16.100.56: This is not a bug. see squid.conf extension_methods
2010/01/31 19:58:41| clientParseRequestMethod: Unsupported method in request
'____;__w_____o'
2010/01/31 19:58:41| clientProcessRequest: Invalid Request
Prevent 172.16.100.56 from sending invalid HTTP requests to your Squid
server. Pulling the Ethernet cable, shutting the switch port or adding
a software firewall rule preventing communications from this host are
all valid (though, nuke-it-from-orbit) methods of achieving this goal.
Identifying the application on this host that is sending the non-HTTP
data to your Squid server and configuring it such that it refrains is
probably a more prudent approach.
Chris
