Brian Rectanus wrote: > > > Yeah, I end up setting on every request. Some further patching I > would like to do is add the ability for mod_proxy_balancer to actually > add/remove the cookie if you use something like > store-route=cookie:MYCOOKIE or similar.
To be honest I do not like this idea. The first assumption is that the backend can do what is needed. If it is *not* capable of doing so there should be a possibility to do this inside httpd (which is currently not working perfectly with the patch), but this should not cause us to reinvent the wheel inside mod_proxy_balancer. I am thinking more along the lines of having SetEnvIf to be able to process things on responses. I admit that your store-route may be easier to configure, but if we add the needed conf stuff discussed above to the docs I think it would be as easy for users to set this up as it is with store-route. Regards RĂ¼diger
