[
https://issues.apache.org/jira/browse/HTTPCORE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155473#comment-17155473
]
Michael Osipov edited comment on HTTPCORE-637 at 7/10/20, 9:18 PM:
-------------------------------------------------------------------
I would say no. The current one, e.g, RFC 3986. If this will be superseded we'd
need to move to the new RFC. I wouldn't want to make it too difficult. It has
caused to much grief in the past for us.
was (Author: michael-o):
I would say now. The current one, e.g, RFC 3986. If this will be superseded
we'd need to move to the new RFC. I wouldn't want to make it too difficult. It
has caused to much grief in the past for us.
> Provide a state of the art RFC 3986 compliant URI class
> -------------------------------------------------------
>
> Key: HTTPCORE-637
> URL: https://issues.apache.org/jira/browse/HTTPCORE-637
> Project: HttpComponents HttpCore
> Issue Type: New Feature
> Components: HttpCore
> Affects Versions: 5.0.1
> Reporter: Michael Osipov
> Priority: Major
>
> Many many times issues cropped up about character equivalence, normalization
> and broken implementation of {{java.net.URI}}. We require or own
> implementation which implements RFC 3986 properly, levaing the former aside
> and avoid long long discussions with users.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
