> Ryan Bloom wrote: > > > > 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. > > If you add the mod_header filter using ProxyAddInputFilter, and you > issue the command: > > Header set X-Test blah > > How does mod_headers know whether the above directive applies to the > frontend normal filter chain, or the backend one? > > I imagine the current behavior will be that mod_headers will be run > twice - once on the front, once on the back.
You re-write the proxy code so that ProxyPass can be put inside of a <Proxy> block. Then, you only specify the individual headers for each block. Ryan
