Any thoughts, on how to handle this? I wish, squid would handle this case gracefully somehow.Its not HTTP; it doesn't really matter if its HTTP-like. Steven Wilton has some patches to Squid-2.6 which implement "full transparency" on non-HTTP looking data; perhaps you want to use those.
Just in case, you didn't know already:This ICY crap (yes, i call it crap, because a HTTP-request deserves a HTTP response, and sending this ICY crap instead is really a bad idea, whoever had it) seems to be pretty wide spread. Just checked many of the streams at shoutcast.com.
But you never heard about that? Am i the first one who complains?I expected this "full transparency" to be a standard feature because of this mess out there in the net. Maybe even configurable (enable transparent mode depending on a regular expression analysing the first line of the reply).
Can this HTTP 0.9 support be switched off somehow? If the first line of the reply is not "HTTP.*", then i don't want it ...
Regards, Sven
signature.asc
Description: OpenPGP digital signature
