Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Message-ID: <764CA2FF49EC054BA086FC8253A52DD7432C4C@merc09.na.sas.com>
From: Larry Isaacs <Larry.Isaacs@sas.com>
To: "'tomcat-dev@jakarta.apache.org'" <tomcat-dev@jakarta.apache.org>
Subject: RE: TC 3.3: getRequestURI()
Date: Wed, 26 Sep 2001 09:02:42 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"


> -----Original Message-----
> From: Bojan Smojver [mailto:bojan@binarix.com]
> Sent: Wednesday, September 26, 2001 7:41 AM
> To: Tomcat Dev List
> Subject: TC 3.3: getRequestURI()
> 
> 
> The latest TC 3.3 CVS with its mod_jk, gives an encoded URI, together
> with the session ID on HttpServletRequest.getRequestURI().
> 
> Example:
> 
> /login/login.vm%3bjsessionid=q95pbsuof1
> 
> Previously, jsessionid wasn't there. The change was 
> intentional, right?

Probably not.  It's a side of effect of the last change which was
to use "s->req_uri = ap_escape_uri(r->pool, r->uri);". This looks
like a good example of a re-encoded URI not being equal to the
original.

Thanks for noticing this.

Larry