On Fri, Feb 4, 2011 at 9:37 PM, Willy Tarreau <[email protected]> wrote: > Hi Jan-Frode, > > On Fri, Feb 04, 2011 at 03:15:49PM +0100, Jan-Frode Myklebust wrote: >> We're trying to filter out HTTP HEAD requests using haproxy, >> to make the proxy behave like shoutcast servers, ref: >> >> http://comments.gmane.org/gmane.comp.web.haproxy/2961 > > But why the hell are your trying to deliberately break HTTP ?
Because that´s what shoutcast seems to be -- HTTP/0.9 with some custom ICY-headers. > It might be a lot better for the long term to fix the server > instead, or you'll constantly have to resort to dirty tricks > to achieve that. Unfortunately I don´t control the servers (or protocol). I have lots of STBs on private networks (rc1918), no NAT, and need to give them access to various shoutcast servers on the Internet. But I guess I´ll need to find some other solution.. look into shoutcast proxy servers, or see if we can configure the clients to use squid + the upgrade_http09 option. http://www.squid-cache.org/Doc/config/upgrade_http0.9/ > > From RFC2616 par.5.1.2: > > The methods GET and HEAD MUST be supported by all general-purpose > servers. All other methods are OPTIONAL. Wrong RFC in this case.. :-) http://www.w3.org/Protocols/HTTP/AsImplemented.html > I'd say that the fact that your client behaviour have changed to something > even dirtier might be an indication that what you're doing is wrong. I don´t disagree.. Will go looking for a better solution. Thanks! -jf
