Re: [squid-users] many parseHttpRequest: Unsupported method found
Siu-kin Lam wrote: Dear all I am using version2.7 stable 3 as a proxy server. I have found many parseHttpRequest: Unsupported method in cache.log. Is it possible to fix it? If you know what the methods are supposed to be. Squid 2.x has a squid.conf option extension_methods ... which allows you to name up to 20 new ones which are allowed through. http://www.squid-cache.org/Versions/v2/2.7/cfgman/extension_methods.html Also, could it change to allow any Unsupported method by default ? The change is not easy and we have already done it in Squid 3.1 (currently 3-HEAD) with no intentions on back-porting. Amos -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7
Re: [squid-users] many parseHttpRequest: Unsupported method found
Hi Amos Thanks for the reply. I found most unsupported method in cache.log are control-code included. I think they are come from some BT clients. Thanks S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 9:44 AM Siu-kin Lam wrote: Dear all I am using version2.7 stable 3 as a proxy server. I have found many parseHttpRequest: Unsupported method in cache.log. Is it possible to fix it? If you know what the methods are supposed to be. Squid 2.x has a squid.conf option extension_methods ... which allows you to name up to 20 new ones which are allowed through. http://www.squid-cache.org/Versions/v2/2.7/cfgman/extension_methods.html Also, could it change to allow any Unsupported method by default ? The change is not easy and we have already done it in Squid 3.1 (currently 3-HEAD) with no intentions on back-porting. Amos -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7
Re: [squid-users] many parseHttpRequest: Unsupported method found
Siu-kin Lam wrote: Hi Amos Thanks for the reply. I found most unsupported method in cache.log are control-code included. I think they are come from some BT clients. Ah, in that case there is nothing that can be done in squid. You need to educate users on proper use of proxies with BT, if you think its worth the effort. Amos Thanks S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 9:44 AM Siu-kin Lam wrote: Dear all I am using version2.7 stable 3 as a proxy server. I have found many parseHttpRequest: Unsupported method in cache.log. Is it possible to fix it? If you know what the methods are supposed to be. Squid 2.x has a squid.conf option extension_methods ... which allows you to name up to 20 new ones which are allowed through. http://www.squid-cache.org/Versions/v2/2.7/cfgman/extension_methods.html Also, could it change to allow any Unsupported method by default ? The change is not easy and we have already done it in Squid 3.1 (currently 3-HEAD) with no intentions on back-porting. Amos -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7 -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7
Re: [squid-users] many parseHttpRequest: Unsupported method found
Hi Amos is this kind connection harmful for Squid daemon? I meant Besides Squid drop this connection, would this kind of connection cause unstable to the daemon ? Also, how could I know the destination IP/host of this kind of connections ? I could find the client (source) IP address from access.log only. Thanks Best Regards, S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 11:35 PM Siu-kin Lam wrote: Hi Amos Thanks for the reply. I found most unsupported method in cache.log are control-code included. I think they are come from some BT clients. Ah, in that case there is nothing that can be done in squid. You need to educate users on proper use of proxies with BT, if you think its worth the effort. Amos Thanks S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 9:44 AM Siu-kin Lam wrote: Dear all I am using version2.7 stable 3 as a proxy server. I have found many parseHttpRequest: Unsupported method in cache.log. Is it possible to fix it? If you know what the methods are supposed to be. Squid 2.x has a squid.conf option extension_methods ... which allows you to name up to 20 new ones which are allowed through. http://www.squid-cache.org/Versions/v2/2.7/cfgman/extension_methods.html Also, could it change to allow any Unsupported method by default ? The change is not easy and we have already done it in Squid 3.1 (currently 3-HEAD) with no intentions on back-porting. Amos -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7 -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7
Re: [squid-users] many parseHttpRequest: Unsupported method found
Hi Amos is this kind connection harmful for Squid daemon? I meant Besides Squid drop this connection, would this kind of connection cause unstable to the daemon ? Not. Squid dumps the TCP connection as soon as the error is found and reported. Also, how could I know the destination IP/host of this kind of connections ? I could find the client (source) IP address from access.log only. Squid never handled the request so never had the destination info. Amos Thanks Best Regards, S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 11:35 PM Siu-kin Lam wrote: Hi Amos Thanks for the reply. I found most unsupported method in cache.log are control-code included. I think they are come from some BT clients. Ah, in that case there is nothing that can be done in squid. You need to educate users on proper use of proxies with BT, if you think its worth the effort. Amos Thanks S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 9:44 AM Siu-kin Lam wrote: Dear all I am using version2.7 stable 3 as a proxy server. I have found many parseHttpRequest: Unsupported method in cache.log. Is it possible to fix it? If you know what the methods are supposed to be. Squid 2.x has a squid.conf option extension_methods ... which allows you to name up to 20 new ones which are allowed through. http://www.squid-cache.org/Versions/v2/2.7/cfgman/extension_methods.html Also, could it change to allow any Unsupported method by default ? The change is not easy and we have already done it in Squid 3.1 (currently 3-HEAD) with no intentions on back-porting. Amos -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7 -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7
Re: [squid-users] many parseHttpRequest: Unsupported method found
Hi Amos I understand. Thanks for the information Best Regards, S K --- On Fri, 7/4/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: Amos Jeffries [EMAIL PROTECTED], squid-users@squid-cache.org Date: Friday, July 4, 2008, 2:48 AM Hi Amos is this kind connection harmful for Squid daemon? I meant Besides Squid drop this connection, would this kind of connection cause unstable to the daemon ? Not. Squid dumps the TCP connection as soon as the error is found and reported. Also, how could I know the destination IP/host of this kind of connections ? I could find the client (source) IP address from access.log only. Squid never handled the request so never had the destination info. Amos Thanks Best Regards, S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 11:35 PM Siu-kin Lam wrote: Hi Amos Thanks for the reply. I found most unsupported method in cache.log are control-code included. I think they are come from some BT clients. Ah, in that case there is nothing that can be done in squid. You need to educate users on proper use of proxies with BT, if you think its worth the effort. Amos Thanks S K --- On Thu, 7/3/08, Amos Jeffries [EMAIL PROTECTED] wrote: From: Amos Jeffries [EMAIL PROTECTED] Subject: Re: [squid-users] many parseHttpRequest: Unsupported method found To: [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Date: Thursday, July 3, 2008, 9:44 AM Siu-kin Lam wrote: Dear all I am using version2.7 stable 3 as a proxy server. I have found many parseHttpRequest: Unsupported method in cache.log. Is it possible to fix it? If you know what the methods are supposed to be. Squid 2.x has a squid.conf option extension_methods ... which allows you to name up to 20 new ones which are allowed through. http://www.squid-cache.org/Versions/v2/2.7/cfgman/extension_methods.html Also, could it change to allow any Unsupported method by default ? The change is not easy and we have already done it in Squid 3.1 (currently 3-HEAD) with no intentions on back-porting. Amos -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7 -- Please use Squid 2.7.STABLE3 or 3.0.STABLE7
