Icecast dev - Jun 2006 - Problem with some ogg players when using apache 2.0 as a proxy in front of icecast

dstjohn a ?crit :
> I can confirm this same issue, using apache 2 or apache 1 branch as a
> proxy in front of icecast2
> using winamp,real player, wmp, xmms, etc.... the list is long.
>
> I too would be interested in seing a reason for this, im guessing its
> the proxy
> server (apache)  not reading the data fast enough maybe? or sending
> headers to the icecast2 server
> that it doesnt recognize? just some ideas on where to start.
>   
Happy to know that I'm not alone with this strange case.
But adding
      SetEnv downgrade-1.0 1
      SetEnv force-response-1.0 1
into the VirtualHost section solve the problem for apache2.0.54
apache docs explain about proxy-force-response variable, but it's 
useless and not working. Those two are working fine.

The reason I found is that ICECAST is sending HTTP 1.0 header in 
response to a request, but
apache 2 is sending a HTTP1.1 header.
(checked with wget -S)

So maybe apache is encapsulating HTTP1.0 header into HTTP1.1 header, so 
some players are troubled?

Regards,
Chris