Hi Bill.
What I need to do with mod-proxy is have a method of communicating
server notes set from mod-include (or wherever) into the request header
going to the application server, and also setting notes based on the proxy
response.
so I have 3 options (as I can see):
* modify mod_proxy so that it has the feature I need
* write specific hook(s) so that I can call another module
* do it via filter(s)
The discussion on the proxy list was that filters was the best design,
and freed the module writer from doing a lot of proxy specific work
To get myself going, I wrote (its floating in the modproxy-dev mailing list)
which implements the hooks
> -----Original Message-----
> From: Bill Stoddard [mailto:[EMAIL PROTECTED]]
> Sent: Fri, May 18, 2001 7:02 AM
> To: [EMAIL PROTECTED]
> Subject: Re: mod_headers
>
>
> >Bill Stoddard wrote:
>
> >> The new mod_header looks pretty good. +1 for commiting it
> provided we
> either
> >> enable Apache to allow modules to insert input filters or
> we remove the
> >> HeaderIn stuff from mod_header.
>
> > The HeaderIn stuff was originally a feature request for
> mod_proxy, where
> > people could modify headers on requests to backend servers. Fiddling
> > with headers is the job of mod_headers, which is why that
> was where the
> > modification was made.
>
> > Lack of support for input filters is a bug - down the line
> there will be
> > more applications for input filters that we haven't foreseen yet - I
> > vote it be fixed.
>
> > Regards,
> > Graham
>
> I believe I understand this now.. :-)
>
> If we want to implement HeadersIn processing as a true filter
> (which is a
> bad idea IMO), then we need to register the filter with the
> pre_connection
> hook. This has serious limitations though. First, a HeadersIn
> can only live
> at server scope (since we have not walked the
> directory/location tree).
> Second, throwing SSL into the picture can complcate things as well.
>
> So now I have a question. What specifically does mod_proxy
> need in the way
> of HeadersIn processing? It is easy enough to modify
> r->headers_in at a hook
> after the headers have been read in but before any request
> body (if any)
> processing. I suspect the mod_proxy requirement can be met
> w/o input header
> filtering.
>
> Bill
>
>
