Re: Issue 2618, jsessionid, exception on first contact
Johannes Hoechstaedter <[email protected]> Thu, 30 Oct 2008 16:56:00 +0100
| Newsgroups | gmane.comp.java.scarab.devel |
|---|---|
| Message-ID | <[email protected]> |
Which upgrade do you mean? Völker Ronny schrieb: > I think, we have to handle this. > As I said in http://scarab.tigris.org/servlets/ReadMsg?list=dev&msgNo=14555 this bug was introduced with the upgrade of the integrated tomcat. > Right now, I'm not sure, if it's our fault or tomcats fault. > > Ronny > -----Original Message----- > From: Johannes Hoechstaedter [mailto:[email protected]] > Sent: Thursday, October 30, 2008 4:25 PM > To: [email protected] > Subject: Re: Issue 2618, jsessionid, exception on first contact > > Do we have to handle this or this this a fault from my side/Browser? > > Völker Ronny schrieb: > >> I think, I have a clue: >> http://scarab.tigris.org/servlets/ReadMsg?list=dev&msgNo=14555 >> >> The first request after a restart seems to contain no session cookie. >> This leads the tomcat to assume that cookies are disabled. >> That's why it attaches the jsessionid to the url. >> In the second request, the session cookie is transmitted, but also the jsessionid in the url. >> In that case, the tomcat seems not to strip of the jsessionid from the pathInfo, which later leads to the exception. >> >> Ronny >> >> >> -----Original Message----- >> From: Johannes Hoechstaedter [mailto:[email protected]] >> Sent: Thursday, October 30, 2008 3:50 PM >> To: Dev List Scarab >> Subject: Issue 2618, jsessionid, exception on first contact >> >> hi filks, >> >> I am a little bit confused. When I restart by borwer, scarab attachs the >> jsessionid to each link, so every first contact with scarab crashes. Do >> somebody know why? >> >> cheers >> Johannes >> >> --------------------------------------------------------------------- >> 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] >> >> >> >> > > --------------------------------------------------------------------- > 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] > > >