DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36737>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36737 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW ------- Additional Comments From [EMAIL PROTECTED] 2005-09-20 20:00 ------- It doesn't matter if the backend server replies with HTTP/1.1 200 OK or with ICY 200 OK. I have tested it with both and mod_proxy does not preserve headers coming from back end server. If my back end server sends Content-Type: audio/mpeg apache mod_proxy will put my header as a part of content and write its own header Content-Type: text/plain There should be a way to tell mod_proxy not to do this and let the backend server send the headers to the client. \ Example: HTTP/1.1 200 OK or ICY 200 OK (doesn't make any difference) icy-notice1:MuziK stream server icy-notice2:Use winamp or media player to stream icy-genre:Mixed icy-name:test-song icy-url:www.example.com icy-metaint:8192 icy-br:56 Connection: close Server: 1.0 Content-type: application/ogg Content-length: 10354 Connection: close mod_proxy in this case should not pass its own headers, instead be told that the backend server will do this. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
