You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2002/07/20 08:43:58 UTC
DO NOT REPLY [Bug 6624] -
double encoding of URLs
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=6624>.
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=6624
double encoding of URLs
jsdever@sympatico.ca changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |commons-
| |dev@jakarta.apache.org
AssignedTo|remm@apache.org |commons-
| |dev@jakarta.apache.org
Severity|Normal |Major
Status|REOPENED |NEW
Priority|Other |High
Version|Nightly Builds |2.0 Milestone 1
------- Additional Comments From jsdever@sympatico.ca 2002-07-20 06:43 -------
This will require a patch that includes test cases. Preferably tests that can
be run with test-nohost ant target. Must ensure that the escaping is done at
the "right" time.
<cite href="http://www.ietf.org/rfc/rfc2396.txt">
2.4.2. When to Escape and Unescape
A URI is always in an "escaped" form, since escaping or unescaping a
completed URI might change its semantics. Normally, the only time
escape encodings can safely be made is when the URI is being created
from its component parts; each component may have its own set of
characters that are reserved, so only the mechanism responsible for
generating or interpreting that component can determine whether or
not escaping a character will change its semantics. Likewise, a URI
must be separated into its components before the escaped characters
within those components can be safely decoded.
</cite>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>