On Tue, 2007-04-03 at 15:06 +0200, Mladen Turk wrote: > Plüm wrote: > > > > > > IMHO adding config parameters is no blocker for a backport. > > I was under different perception. > > > > >> It is probably more easy to add balancer->stickyurl = > >> "jsessionid" when > >> balancer->sticky is "JSESSIONID" and NULL otherwise. > >> > >> Or in get_path_param() test for "jsessionid" when balancer->sticky is > >> "JSESSIONID". > > > > I think we should not hardcode JSESSIONID here. > > We could do that then by using existing directive and decide > during configure time. > For example: > > stickysession="JSESSIONID [C]" stickysession=";jsessionid [P]"
Does that mean that stickysession="JSESSIONID" will work as it does now? I don't think we need "Case insensitive" because that is the Cookie name, the parameter name or the EnvVar name. Those values are normaly well defined. So that would be something: stickysession=JSESSIONID stickyurl=jsessionid stickyenv=MYSESSION Cheers Jean-Frederic > > So instead overwriting the balancer->sticky we could create > an fixed array instead, and have multiple of them. > The param in square brace is optional and would mean: > > [C] -> Cookie Case sensitive > [c] -> Cookie Case insensitive > [P] -> URL Path Case sensitive > [p] -> URL Path Case insensitive > [E] -> EnvVar Case sensitive > [e] -> EnvVar Case insensitive > etc ... > > In case the params are omitted the behavior would be > as follows: > stickysession="JSESSIONID" -> balancer->sticky-[0] > stickysession=";jsessionid" -> balancer->sticky-[1] > stickysession="FOO" -> balancer->sticky-[2] > > > How that looks? > > Regards, > Mladen.
