-----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
>> getRequestURI doesn't get it back. :-/ 

No, I tell that getRequestURI in Tomcat returns file name only - and I'm FINE with 
that.

While, in JRun getRequestURI returns  file name + jsessionid - and I'm not FINE with 
that.

Macromedia support tells that Jrun behavior is according to the specification, and
that all other AS are wrong and JRun is right in this particular case.



Then, who IS right?





I'll buy that - especially since
you're quoting it from the docs ;-) *feels stupid*

Is it a usage question rather than an implementation question? You can
get the querystring too. It does make for another call - but you can
bypass the expense of the concatenation by just printing them out
adjacent. Right?

Thinking ...

Eddie

Bill Barker wrote:

>Hum, it does look like the spec is a bit schizophrenic here.  The
>;jessionid= isn't part of the requestURI in section 4.4:
><spec-quote section="4.4" version="2.3">
>It is important to note that, except for URL encoding differences between
>the
>request URI and the path parts, the following equation is always true:
>
>requestURI = contextPath + servletPath + pathInfo
></spec-quote>
>
>However, in section 15.1.3 it very clearly is:
><spec-quote section="15.1.3" version="2.3>
>public java.lang.String getRequestURI()
>
>Returns the part of this requestfs URL from the protocol name up to the
>query
>string in the first line of the HTTP request.
></spec-quote>
>
>Off-hand, I'd say that it's a good question for
>[EMAIL PROTECTED] so that it can be clarified in the up-coming
>2.4 spec.
>


--
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]>

Reply via email to