> -----Original Message----- > From: Graham Leggett [mailto:[EMAIL PROTECTED] > Sent: Wed, May 16, 2001 4:46 PM > To: [EMAIL PROTECTED] > Subject: Re: [PATCH] Reverse Proxy HTTP Hooks > > > Ian Holsman wrote: > > > > > > I know I could rewrite this as a filter, but I don't know > how to 'add' the filters to the > > proxy request as the syntax is too limiting. > > Hooks again are very proxy specific - I am trying really hard to get > away from proxy specific stuff. They spelled doom for the 1.3 > proxy, and > things have vastly improved since things became more modular and more > simple. > > In theory the existing Set(In|Out)putFilter directives should > allow you > to do exactly what you need to do without any modification to the > existing proxy code at all. Write an input filter to handle the stuff > before the connection, and the output filter will handle > stuff you need > after the connection. Make sure that whatever filter you use is > triggered only on certain URLs, this way you can ensure the > filter only > runs when used as a subrequest from mod_include, and not otherwise. >
ok .. I would have something like this in the config file ProxyPass /m/ http://app:80/ <Location /m/> SetInputFilter HANDYDANDYINFILTER SetOutputFilter HANDYDANDYOUTPUTFILTER </Location> ??? If this is all that needs to be done then I'll change the code to a filter (which I actually agree with you would be nicer) > Of course example code to start with is a huge help, and from my > experience with mod_headers there doesn't seem to be any at > the moment. does mod_case_filter_in.c in the experimental directory work? > Once I have finished with mod_headers though check there, as it is a > rather simple example of an input filter and an output filter (as soon > as I can get the &^%%#^% input filter to work). I'll grab your modified mod_header and see if I can get it going. > > Regards, > Graham > -- > ----------------------------------------- > [EMAIL PROTECTED] "There's a moon > over Bourbon Street > tonight..." >
