On Fri, Jun 13, 2014 at 4:39 PM, Christopher Schultz <ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > James, > > On 6/13/14, 4:11 PM, James H. H. Lampert wrote: >> When this thread first came up, I tried one obvious approach: >> creating a symbolic link in the file system, mapping a new >> directory name into an existing context's directory. >> >> It didn't work. > > If it did work, what you'd end up with is double-deployment, which is > something the OP wanted to avoid. > > If the lb is the problem, the solution is to make the canonical "name" > of the application one that does not include an underscore. Then, use > something like url-rewrite (or, even better, do it at the lb) to > *redirect* users permanently from the "old" URL space to the new URL > space. > > Or, just get a load-balancer that doesn't fall-over when you have > underscores in your URLs. That's just plain bad software. :( > > - -chris
I couldn't agree more re "bad software" and I'll go ahead and name names. It's an Amazon "elastic load balancer". It's configured to provide session affinity using the JSESSIONID cookie. When tomcat sets the JSESSIONID it uses "path=/the_context". The ELB then sets its AWSELB cookie with "path=/the%5Fcontext". I don't know if that's valid per the cookie "spec", but that doesn't matter b/c neither Firefox nor Chrome will return the AWSELB cookie w/ the underscore encoded like that. This of course breaks the session affinity causing all sorts of annoying problems. I may open an issue w/ Amazon about it, but there is no telling when (if) they'd bother to fix it. So I'm pursing other options as well. Thanks again for the suggestions, Colin --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
