[ https://issues.apache.org/jira/browse/HTTPCLIENT-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813865#comment-16813865 ]
Varun Nandi commented on HTTPCLIENT-1968: ----------------------------------------- Can someone confirm if the following is correct? To keep my application behavior (regarding uri normalization) same as 4.5.6, I need to set *{color:#333333}setNormalizeUri{color}* in *RequestConfig* to *false* in *v4.5.8*. This keeps the behavior same for special characters like "/", "+". Any other special characters that are still affected? Thanks. > 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 > Fix For: 4.5.8, 5.0 Beta4 > > Attachments: rewrite_preserve_forward_slash.diff > > Time Spent: 3.5h > Remaining Estimate: 0h > > 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