[
https://issues.apache.org/jira/browse/HTTPCLIENT-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788228#comment-16788228
]
Gary Russell edited comment on HTTPCLIENT-1968 at 3/8/19 7:59 PM:
------------------------------------------------------------------
When do you expect to release 4.5.8? Spring Boot upgraded to 4.5.7 and they,
reasonably, don't want to drop back to 4.5.6 because there are a number of
important fixes in 4.5.7.
The RabbitMQ [REST API |https://pulse.mozilla.org/api/] extensively uses
{{%2F}} in URLs because it is the default virtual host.
e.g. /api/exchanges/<vhost>/<name> gets the exchange info for _name_ in _vhost_
so {{/api/exchanges/%2F/foo}} is broken.
So, Spring Boot users wishing to use the RabbitMQ rest API have to override the
version back to 4.5.6 (and lose all the goodness in 4.5.7).
Boot's next scheduled release is March 29, so before then would be excellent!
Thanks.
was (Author: grussell):
When do you expect to release 4.5.8? Spring Boot upgraded to 4.5.7 and they,
reasonably, don't want to drop back to 4.5.6 because there are a number of
important fixes in 4.5.7.
The RabbitMQ [REST API |https://pulse.mozilla.org/api/] extensively uses
{{%2F}} in URLs because it is the default virtual host.
e.g. /api/exchanges/<vhost>/<name> gets the exchange info for _name_ in _vhost_
so {{/api/exchanges/%2F/foo}} is broken.
So, Spring Boot users wishing to use the RabbitMQ rest API have to override the
version back to 4.5.6 (and lose all the goodness in 4.5.7).
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: [email protected]
For additional commands, e-mail: [email protected]
