Remy Maucherat schrieb: > On Wed, 2008-09-24 at 16:23 +0100, Mark Thomas wrote: >> The draft is here: >> http://jcp.org/en/jsr/detail?id=315 >> >> I though you were on the Servlet EG or am I mistaken? > > I was not aware of that file for whatever reason. I now remember the > language that was discussed, and I remember being in favor of it. It now > tolerates proprietary configuration of the cookie name, but does not > actually mandate or change anything. > >>> I think per context would be a big problem for proxies, so I am against >>> it. There's no need for a patch to state that, I think. >> Certainly, if they were looking at the cookie to manage load-balancing or >> similar then different values per context would make that configuration >> more complex than it needs to be. > > I am -1 for per context configuration, +1 for global configuration (and > I know JF has a custom patch to do that, which I think also does the URL > parameter).
If I read Mladen's latest patch to mod_jk (done yesterday or so) correctly, the values will already be configurable per mount (we will have a concept of mount extensions, which does make some configuration options adjustable per mount, like e.g. reply_timeouts). So the concept specific part of it would not really be a technical problem for mod_jk 1.2.27+. For httpd/mod_proxy_balancer you can configure those data via Proxy blocks, which should also work per mount. A proxy needs to integrate various types of backends, so at least mod_proxy needs that type of flexibility since other backends use other types of session identifiers (e.g. PHP). Whether it's good practise is surely questionable. E.g. I like logging the session cookies in the httpd access log, but that's not that easy, if there are a lot of different cookies in use for that purpose. So it does make your life more complicated, but at least proxies do not have a problem with it, or will soon not have a problem with it. Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
