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 2003/01/16 20:11:05 UTC
DO NOT REPLY [Bug 12798] -
About HttpMethodBase
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=12798>.
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=12798
About HttpMethodBase
------- Additional Comments From armando.anton@newknow.com 2003-01-16 19:11 -------
I don't understand why the path is encoded but the queryString not
I think it is a bug and the path must not be encoded because the path and query
are well-formed in this point and encoding them can cause unexpected behaviours
(more info)The query encoding was removed in revision 1.69
HttpMethodBase v1.95 (generateRequestLine method). Current code:
StringBuffer buf = new StringBuffer();
String path = null;
try {
path = (requestPath == null) ? "/" : URIUtil.encodePath
(requestPath);
} catch (URIException urie) {
log.error("URI path encoding error");
path = requestPath;
}
buf.append(path);
if (query != null) {
if (query.indexOf("?") != 0) {
buf.append("?");
}
String queryString = null;
queryString = (query == null) ? "/" : query;
buf.append(queryString);
}
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>