You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Sam Berlin (JIRA)" <ji...@apache.org> on 2008/01/22 15:08:34 UTC
[jira] Commented: (HTTPCLIENT-730) Use of Multi-Args URI Causes
URI-Rewriting to improperly unescape characters
[ https://issues.apache.org/jira/browse/HTTPCLIENT-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561343#action_12561343 ]
Sam Berlin commented on HTTPCLIENT-730:
---------------------------------------
Per the email thread, placing
----
String path = uri.getRawPath();
String query = uri.getRawQuery();
String fragment = uri.getRawFragment();
String newUri =
(path == null ? "" : path)
+ (query == null ? "" : ("?" + query))
+ (fragment == null ? "" : ("#" + fragment));
request.setURI(new URI(newUri));
--
in DefaultClientRequestDirector.rewriteRequestURI else if branch will fix it, but I don't know how stable that is.
> Use of Multi-Args URI Causes URI-Rewriting to improperly unescape characters
> ----------------------------------------------------------------------------
>
> Key: HTTPCLIENT-730
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-730
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.0 Alpha 2
> Reporter: Sam Berlin
> Attachments: TestUriEscapes.java
>
>
> See: http://www.nabble.com/unable-to-encode-reserved-characters-using-java.net.URI-multi-arg-constructors-td14954679.html for information from the httpclient-dev thread. The basic idea is that URI's multi-arg constructors break things.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org