[
https://issues.apache.org/jira/browse/HTTPCLIENT-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756341#comment-16756341
]
Jay Modi commented on HTTPCLIENT-1968:
--------------------------------------
RFC 2396 has very similar text in Section 2.2:
{quote}The purpose of reserved characters is to provide a set of delimiting
characters that are distinguishable from other data within a URI. URIs that
differ in the replacement of a reserved character with its percent-encoded
octet are not equivalent. Percent-encoding a reserved character, or decoding a
percent-encoded octet that corresponds to a reserved character, will change how
the URI is interpreted by most applications. Thus, characters in the reserved
set are protected from normalization and are therefore safe to be used by
scheme-specific and producer-specific algorithms for delimiting data
subcomponents within a URI.{quote}
In section 2.4:
{quote}When a URI is dereferenced, the components and subcomponents significant
to the scheme-specific dereferencing process (if any) must be parsed and
separated before the percent-encoded octets within those components can be
safely decoded, since otherwise the data may be mistaken for component
delimiters. The only exception is for percent-encoded octets corresponding to
characters in the unreserved set, which can be decoded at any time. For
example, the octet corresponding to the tilde ("~") character is often encoded
as "%7E" by older URI processing implementations; the "%7E" can be replaced by
"~" without changing its interpretation.{quote}
I have already used the workaround of determining if the URI needs to be
relative or absolute in my application, but I don't think this should be
expected for users of httpclient.
> Encoded forward slashes are not preserved when rewriting URI
> ------------------------------------------------------------
>
> Key: HTTPCLIENT-1968
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1968
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 4.5.7
> Reporter: Jay Modi
> Priority: Major
> Attachments: rewrite_preserve_forward_slash.diff
>
>
> URIs that contain an encoded forward slash (%2F) are no longer preserved when
> the HTTP client executes. I came across this when upgrading from 4.5.2 to
> 4.5.7 and my requests that contained an encoded forward slash suddenly
> started failing. The appears to be due to decoding and re-encoding of the
> path that takes place in the URIUtils#rewriteURI method. I've attached a
> patch that restores the old behavior but if a URI contains two slashes in a
> row in addition to an encoded slash the encoded forward slash will be decoded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
