Hi Mark, So this means that the JSESSIONID is no longer removed from the requestURL by tomcat (and is thereby now propagated all the way) and we as developers of our product must now take that in consideration that JSESSIONID is returned as part of the URI when calling for example httpServletRequest.getRequestURI()? So what you are saying is that this is a new behavior in tomcat 6.0.35, is this stated somewhere in the changelog?
//Daniel Jan 16, 2012 kl. 2:04 PM skrev Mark Thomas: > On 16/01/2012 12:45, Daniel Pyykkö wrote: >> Hi, >> >> I seem to have found a problem in tomcat 6.0.35 that did not exist in >> 6.0.32 or prior to that version that I would like to know if I should >> file as a bug or if it exists a solution to it (it seems to be a >> coding bug but just in case, I run tomcat on a MAC). > > And what exactly is the problem? > >> Now to my problem/question. Is it just a bug that the method >> parseSessionId is no longer called by the method postParseRequest or >> how/where should the JSESSIONID be removed from the requestURL? Or >> could it be on purpose that the JSESSIONID no longer is removed from >> the requestURL? > > The change is deliberate. JSESSIONID is a valid path parameter. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
