I disagree entirely. You should be -able- to do so, without being forced to do so.
The simple fix is not to define the default content type in the root of the <Proxy > directive. However, there seems no 'trivial' way to do so, unless <Proxy *> would accomplish this. If we don't support a 'none' option to the default content type directive, we aught to do so. Bill At 11:12 PM 2/28/2002, you wrote: >Hi all, > >Recently someone noted that certain parts of Ebay didn't work via >mod_proxy. This was because the pages in question had no content-type >header, and Apache was adding a default header "text/plain", which >caused browsers to display the source of the page. > >The resulting discussion said that proxy should just send through no >content-type header if one was not supplied, and let the borwser handle >the brokenness. However - the code that actually adds the content-type >when it is missing sits in make_content_type() in http_protocol.c. > >So - the fix seems to be to change make_content_type() to return NULL if >the incoming content-type is missing. But - will this break anything >else...? > >Regards, >Graham >-- >----------------------------------------- >[EMAIL PROTECTED] "There's a moon > over Bourbon Street > tonight..."
