> -----Original Message----- > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 19, 2003 11:19 AM > To: [EMAIL PROTECTED] > Subject: Re: Possible problem with the new URI code > > > "Quinton McCombs" <[EMAIL PROTECTED]> writes: > > >I can not reliably recreate this problem. All that is > required is to > >close all instances of my web browser and then access the > site again. > >Stepping through the code with my debugger, I found that the problem > >occurs on line 535 of BaseURI. This is a call to > response.encodeURL(). > >This is where the ;jsessionid=xxx is appended to the end. > > If this really is a container problem, then we should think > about adding a property for the content tool to never encode > the jsession id (just as the old 2.2 code did).
Allowing ContentTool to be configured not to call encodeURL() has fixed my problem. I posted a separate message to the dev list with an approach to allow configurable tools. Assuming this is approach is agreeable to everyone, I will commit the changes. > Hm. One more item on my todo list. :-/ > > 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]
