On Tue, 28 Nov 2000, Gunther Birznieks wrote:
> Dave's company could also *pay* someone to do what he wants. It would
> probably take about a day of someone at Covalent (probably less) to whip
> something up to stop doing the headers (and they would probably be able to
> feed the change back into
Dave's company could also *pay* someone to do what he wants. It would
probably take about a day of someone at Covalent (probably less) to whip
something up to stop doing the headers (and they would probably be able to
feed the change back into the mod_proxy part of the Apache CVS directly so
o
On Mon, 27 Nov 2000, Sander van Zoest wrote:
> Ah, are you trying to send ICY headers or something? mod_proxy only knows
> of HTTP and sends the appropriate status itself rather then what it
> gets from the remote server. This will also require some hacks in
> mod_proxy to make it aware of the pr
Dave Rolsky <[EMAIL PROTECTED]> writes:
> I'm afraid of C.
Don't be. (perl is C with cream and sugar added ;) Grab
a copy of Kernighan and Ritchie's _The C Programming Language_
(it's authoritative, and all of 274 pages cover to cover).
Then start monkeying around in src/modules/proxy/proxy_h
On 27 Nov 2000, Joe Schaefer wrote:
> mod_proxy will upgrade assbackwards requests to HTTP/1.0
> before passing them along to the backend server, which may
> explain why the date field shows up in your telnet experiments.
> Why not post the full output of your telnet sessions so we
> can see what
Dave Rolsky <[EMAIL PROTECTED]> writes:
> On Mon, 27 Nov 2000, Sander van Zoest wrote:
>
> > Normally the mod_proxy code doesn't touch the headers, it simply sends
> > the headers on from the remote server you are proxying too. I doubt
> > it is mod_rewrite but it could be. The extra headers are
On Mon, 27 Nov 2000, Sander van Zoest wrote:
> Ah, are you trying to send ICY headers or something? mod_proxy only knows
> of HTTP and sends the appropriate status itself rather then what it
> gets from the remote server. This will also require some hacks in
> mod_proxy to make it aware of the pr
On Mon, 27 Nov 2000, Dave Rolsky wrote:
> On Mon, 27 Nov 2000, Sander van Zoest wrote:
> > Normally the mod_proxy code doesn't touch the headers, it simply sends
> > the headers on from the remote server you are proxying too. I doubt
> > it is mod_rewrite but it could be. The extra headers are pr
On Mon, 27 Nov 2000, Sander van Zoest wrote:
> Normally the mod_proxy code doesn't touch the headers, it simply sends
> the headers on from the remote server you are proxying too. I doubt
> it is mod_rewrite but it could be. The extra headers are probably coming
> from your remote server you are
On Mon, 27 Nov 2000, Dave Rolsky wrote:
> Actually, something is _adding_ headers and I want it to stop doing it.
> It may not be mod_proxy, perhaps it is mod_rewrite. I really don't know.
Normally the mod_proxy code doesn't touch the headers, it simply sends
the headers on from the remote serv
On Mon, 27 Nov 2000, Sander van Zoest wrote:
> > Unfortunately, it seems that when I proxy I get the above added so I have
> > to serve streaming audio directly from the mod_perl server, which is less
> > than ideal in terms of resource use.
>
> If you mena you rewrite to mod_proxy, then mod_prox
On Sun, 26 Nov 2000, Dave Rolsky wrote:
> This sort of a mod_perl question. When I use mod_rewrite to proxy to my
> mod_perl backend servers, it seems that even if I explicitly don't send
> headers I still get something like:
>
> Unfortunately, it seems that when I proxy I get the above added s
This sort of a mod_perl question. When I use mod_rewrite to proxy to my
mod_perl backend servers, it seems that even if I explicitly don't send
headers I still get something like:
HTTP/1.0 OK
Date: blah bah
in front of anything I said. The issue here is that I wrote some MP3
serving code based
13 matches
Mail list logo
