I *think*, from quick source code scanning, that JK does not call SetHeader with the correct/complete URL, whereas JK2 does.
Can anyone verify this? Thanks, Derrick -----Original Message----- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Thursday, December 16, 2004 1:46 PM To: Tomcat Developers List Subject: Re: JK 1.2.7 beta 3 + URL rewriting scheme issue Derrick Koes wrote: > > From the JK debug log, I suspect the jsessionid part of the URL is being > dropped somewhere between these two log lines. Or, I suppose it could be > added to the header. In any event it is not longer part of the URL. If > anyone has any further insight that would be most helpful. > > [Thu Dec 16 11:37:58 2004] [5228:5468] [debug] jk_isapi_plugin.c > (753): Virtual Host redirection of > /dkoesxp/ilt/rd/8a3c3f8d03bf435b1e1f0ec005b63a8b/ilt/spMySessions.do;j > sessionid=24B27CD241D89FB2A217DF21497E84B3.dkoesxp8009 > [Thu Dec 16 11:37:58 2004] [5228:5468] [debug] jk_uri_worker_map.c > (682): Attempting to map URI > '/dkoesxp/ilt/rd/8a3c3f8d03bf435b1e1f0ec005b63a8b/ilt/spMySessions.do' > from 2 maps > Well that's the essence of the ajp protocol. The jsessionid will be removed from url and hardcoded inside ajp packet. Mladen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
