The servlet spec is pretty clear about where the session id is supposed to be. I don't think it is a good idea to introduce something that violates those requirements (and which would trap unwary developers into dependence on a non-standard implementation of this functionality).
Craig On Fri, 2 Nov 2001, Robert Lucier wrote: > Date: Fri, 2 Nov 2001 13:22:58 -0800 (PST) > From: Robert Lucier <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Meta Refresh and jsessionid - a proposal > > I'm having a seemingly common problem where I can't use url-rewriting > with the <META HTTP-EQUIV="Refresh" tag because the semi-colon in the > rewritten URL is confused with the delimiter in the meta tag. > > I didn't see a solution or workaround, so here's mine. I'd like to > modify the HttpProcessor.parseRequest method to look for "jsessionid=" > in the query string if ";jsessionid" is not found in the uri. That way > the existing encodeURL method will still work, but those who need the > refresh method can put the jsessionid in the query string parameters. > > Please let me know if this is acceptable or if there is a better way to > solve this problem > > > __________________________________________________ > Do You Yahoo!? > Find a job, post your resume. > http://careers.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
