It would need to be called >inside< the proxy_http/ftp/connect code itself not in the mod_proxy.c
the problem graham is having is how do add a 'Header Set X-FOOBAR: 1' so it only gets added to the proxied request and not every request without changing mod_header significantly > -----Original Message----- > From: Ryan Bloom [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 07, 2002 10:31 AM > To: [EMAIL PROTECTED] > Subject: RE: adding another hook to proxy-http > > > > > I need to add another hook to the proxy-http > > > so that I can munge the request to the proxied server. > > > > > > now the standard response is: 'you need a input filter' > > > but I am still unable to get a input filter setup so that > > > it *only* runs on the request going to the proxied server. > > > > > > so I'm going to commit the new hook to proxy-http which allows > > > a module to play with the outgoing request if no one objects, > > > becasue I can't see any way that this can be done without it. > > Does it have to be added to proxy-http or can it be added to the base > proxy code, so that all of the proxy modules can use it? I understand > that the proxy modules would need to understand the protocol they are > filtering, and I haven't worked that out yet. However, one > hook for all > proxy modules sounds better than one hook for each proxy module. > > > Then add a hook to add input and output filters to the > backend filter > > stack, eg ProxyAddInputFilter, ProxyAddOutputFilter. > > > > The challenge of course is to tell a filter (like mod_headers for > > example) that "this config is for the normal stack, and this second > > config is for the backend stack". > > That is easy to do. If you create the ProxyAddFooFilter directives, > that directive adds the filter to the correct filter list, and the > filter just does the right thing. > > Ryan > >
