Why not simply encoding the url ? See <http://nagoya.betaversion.org/bugzilla/show_bug.cgi?id=1482>
Saludos , Ignacio J. Ortega > -----Mensaje original----- > De: craigmcc@localhost [mailto:craigmcc@localhost]En nombre > de Craig R. > McClanahan > Enviado el: viernes 2 de noviembre de 2001 22:59 > Para: Robert Lucier > Cc: [EMAIL PROTECTED] > Asunto: Re: Meta Refresh and jsessionid - a proposal > > > > On Fri, 2 Nov 2001, Robert Lucier wrote: > > > Date: Fri, 2 Nov 2001 13:44:20 -0800 (PST) > > From: Robert Lucier <[EMAIL PROTECTED]> > > To: Craig R. McClanahan <[EMAIL PROTECTED]> > > Subject: Re: Meta Refresh and jsessionid - a proposal > > > > I understand, and that bothers me. Has there been any talk > of modifying > > that portion of the spec to be compatible with the meta-refresh tag? > > The problem shows up on this and other lists fairly frequently. > > > > I don't recall any such discussion -- the best way to make sure it at > least gets paid attention to is to submit feedback to the Servlet Spec > feedback address ([EMAIL PROTECTED]). > > It may also be that the expert group doesn't consider > "compatible with the > meta-refresh tag" to be a very compelling argument: > > - "Refresh" is not a standard HTTP header > > - Browsers that misinterpret this kind of thing: > > <meta http-equiv="refresh" > content="2;URL=http://foo/bar;jsessionid=12345";> > > sound like they are broken in the first place -- they should be > parsing on the first semicolon, not the second one. > > Craig > > > > --- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > > > 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]> > > > > > > > > > > > > > > > > > __________________________________________________ > > 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]>
