DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6643>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6643

Tom 3.3a or 3.31b1 : URLRewriting POST ==> 404 error

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From [EMAIL PROTECTED]  2002-03-08 13:25 -------
Yes : Section 8.1 of the servlet spec (either 2.2 or 2.3) states that I should 
pass a path to getRequestDispatcher, not a URL.  
Yes : If I don't call response.encodeURL on "fenetreSuivante", everything will
work fine. 

But Section 7.1.1 of the Servlet Spec (2.2) states that "The session id must be
encoded as a path parameter in the resulting URL string. ... URL containing
encoded path ..."

Thus, I can consider that, an encoded path (containing the session id) is a
"particular" path that can be passed to getRequestDispatcher.
Furthermore, other Web Application Servers (like Resin for example) consider
this parameter as an encoded path and know how to treat it.
It is also more simple for a programmer to encode "fenetreSuivante" (in my
example) without knowing if this  field will be treated by a sendRedirect, a
getRequestDispatcher(..).forward or other.
I Know I am annoying but I consider this as a bug (not corrected).

thanks.
Yo

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to