bug report was marked as invalid by you with the
indication that getRequestURI delivers a path element, which
according to section 8.4 in the servlet spec should be
altered accordingly when forwarding.
I am not quite sure if this interpretation is true. For one
thing section 4.4 (request path
The "must remain encoded" requirement for getRequestURI(), as was stated
in the response by "lin" on the Macromedia forum thread, refers to any URL
encoding that was done by the client to transmit characters like '/' and
'&' in a URI. This doesn&#
Look at what Bob posted. I'd listen to the spec before I listened to
anyone else - hold that up to their nose. It's black and white.
Alex Kachanov wrote:
>-Original Message-
>From: Eddie Bush [mailto:[EMAIL PROTECTED]]
>To: Tomcat Developers List
>Subject: Re: g
l Message-
From: Bill Barker [mailto:[EMAIL PROTECTED]]
Sent: 11 y| 2002 s. 14:45
To: Tomcat Developers List
Subject: Re: getRequestURI()
- Original Message -
From: "Bill Barker" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
-Original Message-
From: Eddie Bush [mailto:[EMAIL PROTECTED]]
To: Tomcat Developers List
Subject: Re: getRequestURI()
>> Ah - now I feel stupid. I was thinking he was saying encodeURL didn't
>> put it there. According to what your interpretation is he things
>>
- Original Message -
From: "Bill Barker" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 10:34 PM
Subject: Re: getRequestURI()
> Hum, it does look like the spec is a bit schizophrenic here.
Ah - now I feel stupid. I was thinking he was saying encodeURL didn't
put it there. According to what your interpretation is he things
getRequestURI doesn't get it back. :-/ I'll buy that - especially since
you're quoting it from the docs ;-) *feels stupid*
Is it a usage que
stURI = contextPath + servletPath + pathInfo
However, in section 15.1.3 it very clearly is:
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 8:33 PM
Subject: getRequestURI()
Hello!
This is a page:
<%@ page contentType="text/html;charset=Shift_JIS"%>
<%@page session="
Hello!
This is a page:
<%@ page contentType="text/html;charset=Shift_JIS"%>
<%@page session="true"%>
<%= request.getRequestURI() %>
<%= session.getId() %>
So, guys, what do you think "request.getRequestURI()" method should return
when cookies are switched OFF in browser and the request is
ht
Bojan Smojver wrote:
>
> [EMAIL PROTECTED] wrote:
>
> > I don't think I can do this alone ( if it sounded like I volunteer to fix
> > it - well, I need help ).
>
> > - Test.
>
> I'm one of those overly brave and too stupid that put CVS versions of
> software in production environment. Promise
TED]]
>Sent: Monday, October 01, 2001 10:52 PM
>To: [EMAIL PROTECTED]
>Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI()
>
>
>I thought you were talking about the mod_jk in the TC3.3
>branch. If you're talking j-t-c only, then I don't mind an
>Option, as long
1 11:24 AM
| To: [EMAIL PROTECTED]
| Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI()
|
|
| >Why can't we implement the 3.3 collaborative solution in 4.0 ?
| >That would maintain compatibility.
|
| And also in TC 3.2.4 ?
|
| >I just hate to provide an option which could re
AIL PROTECTED]
>| Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI()
>|
>|
>| >What whould happen in 3.3 if ForwardEscapedURI was chosen?
>| >Wouldn't the facade escape it again?
>| >
>|
>| My goal in mod_jk is to keep compatibility with ALL tomcat
orts. I'd hesitate to
add it.
Keith
| -Original Message-
| From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
| Sent: Monday, October 01, 2001 10:35 AM
| To: [EMAIL PROTECTED]
| Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI()
|
|
| >What whould happen in 3.3 if ForwardEsc
>What whould happen in 3.3 if ForwardEscapedURI was chosen?
>Wouldn't the facade escape it again?
>
My goal in mod_jk is to keep compatibility with ALL tomcat
release, TC 3.2, 3.3 and 4.0.
The option will let us configure it, even if by default
mod_jk found in TC 3.3 and J-T-C will use the TC
C 3.3: getRequestURI()
|
|
| >Henri, I do not think this will be useful
| >or necessary with the planned changes. I'd
| >be -1.
| >
| >r->uri will be used, making the mod_rewrite
| >folks happy, and the facade will encode the
| >uri, which implements the spec correctly.
|
t;| Sent: Monday, October 01, 2001 5:18 AM
>| To: [EMAIL PROTECTED]
>| Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI()
>|
>|
>|
>| >- Revert jk/apache to use uri, remove the encode call (
>again, j-t and
>| >j-t-c - one more week to do that, after that we
n Option?
Keith
| -Original Message-
| From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
| Sent: Monday, October 01, 2001 5:18 AM
| To: [EMAIL PROTECTED]
| Subject: RE: Volunteers for: - RE: TC 3.3: getRequestURI()
|
|
|
| >- Revert jk/apache to use uri, remove the encode call ( again, j-t
>- Revert jk/apache to use uri, remove the encode call ( again, j-t and
>j-t-c - one more week to do that, after that we'll be j-t-c
>only ). Henri
>- could you do this and the next one ?
I'll reintroduce the JkOptions which will help us play with
different encoding :
ForwardStandardURI :
wil
rom: "Bill Barker" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Bill Barker"
> <[EMAIL PROTECTED]>
> Sent: Sunday, September 30, 2001 12:40 AM
> Subject: Re: Volunteers for: - RE: TC 3.3: getRequestURI()
>
>
> >
EMAIL PROTECTED]>
Sent: Sunday, September 30, 2001 12:40 AM
Subject: Re: Volunteers for: - RE: TC 3.3: getRequestURI()
> Actually, my original was a straight java.net.URLEncode after stripping
out
> the session id. However, I'm easy. Attached is using UEncoder (which I
> initiall
Barker"
<[EMAIL PROTECTED]>
Sent: Sunday, September 30, 2001 1:23 AM
Subject: Re: Volunteers for: - RE: TC 3.3: getRequestURI()
> On Sat, 29 Sep 2001, Bill Barker wrote:
>
> > It seems that I must have been bad in a past life, since my Karma isn't
high
>
<[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, September 28, 2001 11:17 AM
> Subject: Volunteers for: - RE: TC 3.3: getRequestURI()
>
>
> >
> > It seems most agree on using 'decoded' URI in mod_jk. Making the change
> > is not ea
IL PROTECTED]>
Sent: Friday, September 28, 2001 11:17 AM
Subject: Volunteers for: - RE: TC 3.3: getRequestURI()
>
> It seems most agree on using 'decoded' URI in mod_jk. Making the change
> is not easy, there are few places where we need to coordinate and make
> sure we
>-Original Message-
>From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, September 27, 2001 2:27 AM
>To: [EMAIL PROTECTED]
>Subject: RE: TC 3.3: getRequestURI()
>
>
>I'm +1 for this. It is the best solution.
>
>Keith
>
>| -Origin
- what about integrating with apache, where the decoded
> uri is used for everything ( that means any attempt to
> authenticate using apache modules may create huge problems)
>
> 2. Use a different encoding function, that doesn't
> encode ';'.
> Problems:
> - encodin
I'm +1 for this. It is the best solution.
Keith
| -Original Message-
| From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
|
| 3. Revert to the use of uri ( i.e. the decoded uri ), and
| change the getRequestURI ( the facade ) to generated a
| 'canonical' encoding.
| Problems:
, that doesn't
> encode ';'.
> Problems:
> - encoding/decoding will result in a different URI
> ( thus the servlet spec will not be happy )
> - inconsistency between tomcat standalone and tomcat+server
>
> 3. Revert to the use of uri ( i.e. the decoded uri ), and
&g
;t
encode ';'.
Problems:
- encoding/decoding will result in a different URI
( thus the servlet spec will not be happy )
- inconsistency between tomcat standalone and tomcat+server
3. Revert to the use of uri ( i.e. the decoded uri ), and
change the getRequestURI ( the facade ) to generate
Keith Wannamaker wrote:
>
> 0x3b = ';'. Ignacio is right, SessionID doesn't remove the id
> because it is not expecting ; to be encoded. So now it shows
> up in the URI and has the side effect of breaking sessions
> that depend on url rewriting. But, the spec does say the URL
> should be encod
Yes.
- Original Message -
From: "Keith Wannamaker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 26, 2001 10:57 AM
Subject: RE: TC 3.3: getRequestURI()
> Are you using mod_jk?
>
> | -Original Message-
> | From: Bi
Are you using mod_jk?
| -Original Message-
| From: Bill Barker [mailto:[EMAIL PROTECTED]]
| Sent: Wednesday, September 26, 2001 1:17 PM
| To: [EMAIL PROTECTED]
| Subject: Re: TC 3.3: getRequestURI()
|
|
| I don't get this with RC1. From tomcat-log with debugging enabled for
r" <[EMAIL PROTECTED]>
To: "Tomcat Dev List" <[EMAIL PROTECTED]>
Sent: Wednesday, September 26, 2001 4:41 AM
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.getReq
2:37 PM
| To: [EMAIL PROTECTED]
| Subject: Re: TC 3.3: getRequestURI()
|
|
| "Ignacio J. Ortega" wrote:
| >
| > Probably will be the Session id interceptor that does not understand a
| > encoded jsessionid, not in the mod_jk..
|
| I was thinking that ap_escape_uri was changi
>
> > -Mensaje original-
> > De: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
> > Enviado el: miércoles 26 de septiembre de 2001 16:55
> > Para: [EMAIL PROTECTED]
> > Asunto: RE: TC 3.3: getRequestURI()
> >
> >
> > I'm not sure I unders
Para: [EMAIL PROTECTED]
> Asunto: RE: TC 3.3: getRequestURI()
>
>
> I'm not sure I understand why the session id was not
> also showing up with r->unparsed_uri. I'm doing some
> experimenting now..
>
> Keith
>
> |/login/login.vm%3bjsessionid=q95pbsuof1
I'm not sure I understand why the session id was not
also showing up with r->unparsed_uri. I'm doing some
experimenting now..
Keith
|/login/login.vm%3bjsessionid=q95pbsuof1
| 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)
Larry Isaacs wrote:
>
> > -Original Message-
> > From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, September 26, 2001 7:41 AM
> > To: Tomcat Dev List
> > Subject: TC 3.3: getRequestURI()
> >
> >
> > The latest TC 3.3
> -Original Message-
> From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
> 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
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?
Bojan
40 matches
Mail list logo
