httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36737] New: - mod_proxy should be able to preserve headers from backend
Date Tue, 20 Sep 2005 16:30:05 GMT
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

           Summary: mod_proxy should be able to preserve headers from
                    backend
           Product: Apache httpd-2.0
           Version: 2.0.54
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P4
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: admin@swicago.com


I have a media server running on port 1755 using ICY protocols to inform the 
media client of the data stream it is going to recieve. I decided to use 
mod_proxy to proxypass to my backend server for users that are in enviroments 
that block all ports except 80 and 443
<location /muziK>
ProxyPass http://localhost:1755/
</location>
While testing I discovered that mod_proxy takes all data returned from the 
media server and considers it as content, ignoring my ICY headers, preappending 
its own headers to the data being returned to the requesting client.
Example:
HTTP/1.1 200 OK
Date: Tue, 20 Sep 2005 14:42:45 GMT
Transfer-Encoding: chunked
Content-Type: text/plain


10465
ICY 200 OK
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
MPEG data Stream MPEG data Stream MPEG data Stream

A client recieving this data will consider all of the content as MPEG data.
With this data, the client is unable to determine the media, especially when the
media is a mount or ogg and contains icy-br and icy-metaint. A client streaming 
data with ICY metadata and not knowing of the header icy-metaint, will assume 
the data is mpeg and it will play back, reproducing gliches.
I know I can set or append headers in the location entry of my httpd.conf, but 
that will only allow one type of media and not allow ICY metadata.
Is there a way to turn off all headers produced by mod_proxy, including 
HTTP/1.1 200 OK ??? The backend server should decide if it is 200 OK or not, 
unless backend is not responding. And the backend server should be able to 
passively send its headers through. 

This is reproducible in a win32 and linux configure apache/mod_proxy

Let me know if there is a resolution for this.
Thanks
ALLAN

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message