> -----Original Message----- > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 19, 2003 3:39 PM > To: [EMAIL PROTECTED] > Subject: Re: Possible problem with the new URI code > > > "Quinton McCombs" <[EMAIL PROTECTED]> writes: > > Hm, > > almost all of the Apache-Tomcat-Howto archives suggest using > the Rewrite approach. I'm still not convinced, that this is > _not_ a bug on the Apache httpd side. IMHO, it should > interpret the ;jsessionid=xxx as a path parameter (as > requested by the Servlet 2.2 API spec).
It looks like I might have to use the rewrite approach. I have been trying for the past few hours to get JkMount directives to work. The debug logging for mod_jk seems to indicate that the URL is compared to the regualr expressiong without the ;jsessionid=xxx. This is making it impossible to use JkMount to forward those requests to Tomcat. > Two more things to try out: Which apache do you use? 2.x or > 1.3? And can you try to deploy using mod_webapp? I am using 2.x with mod_jk. > BTW: I just rechecked and at least with Tomcat 4.0.x (I'd > assume that will all other versions after this one, too), we > build the URI as > http://forge.intermeta.de:8080/myfunnyapp/app;jsessionid=40DD4D668F4ACD9 94C5F3BD7639C6AA5?count=1 so the jsession id is put in front of the query parameters. This is how the Servlet Spec suggests by declaring the ;jessionid a path parameter. Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ Java, perl, Solaris, Linux, xSP Consulting, Web Services freelance consultant -- Jakarta Turbine Development -- hero for hire --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
