And thus it came to pass that Thomas Eibner wrote:
(on Fri, Jul 19, 2002 at 01:50:47PM +0200 to be exact)

> On Fri, Jul 19, 2002 at 07:56:58AM +0200, [EMAIL PROTECTED] wrote:
> > Hi all,
> > 
> > First of all, here is the Required Disclaimer: "Hi everybody, I am 
> > insane and new to the list. I am also emotionally very vulnerable and 
> > can not handle rejection very well..." :-)
> > 
> > Ok, now this is out of the way, I would greatly value your thoughts and 
> > opinions about the following:
> > 
> > Due to an "interesting" (which in this case is political correctese
> > for "stupid") networking situation at a customer I am experiencing
> > various problems with incoming and outgoing HTTP headers. There are so
> > many forward and reverse proxies all over the place that all sorts
> > of stuff is going wrong.
> > 
> > Therefore, I am in dire need of an HTTP header rewriting capability
> > that can add, delete *and* rewrite HTTP headers just after coming into
> > the server and just before going out to the browser.
> 
> for 1.3 at least:
> 
> 1) post read request phase
> 2) fixup phase
> 
> And why can't you do that with a simple custom written module?
> 
> -- 
>   Thomas Eibner <http://thomas.eibner.dk/> DnsZone <http://dnszone.org/>

1) is certainly true, but I wonder whether 2) is true...

If I look at the Apache 1.3 source code, it seems to me that it is the
responsibility of the handler routine that generates the content to
add/change any required output headers and then start generating the
content. I took the following from mod_example:

  Since content handlers are dumping data directly into the connexion
  (using the r*() routines, such as rputs() and rprintf()) without
  intervention by other parts of the server, they need to make
  sure any accumulated HTTP headers are sent first.  This is done by
  calling send_http_header().  Otherwise, no header will be sent at all,
  and the output sent to the client will actually be HTTP-uncompliant.

And this is backup up by the code. The "send_http_header" routine in 1.3
has no further hooks to do any rewriting on anything that has been
generated between the call to the handler and the send_http_header()...

I am still looking in the Apache 2.x source trees to see if there's
anything there that can help us....

++Jos.nl





-- 
"Freedom" is just another word for "nothing left to lose"...

Reply via email to