[
https://issues.apache.org/jira/browse/HTTPCORE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155431#comment-17155431
]
Gary D. Gregory edited comment on HTTPCORE-637 at 7/10/20, 12:22 PM:
---------------------------------------------------------------------
Would we consider supporting different RFCs clearly and separately? I'm
concerned that a kitchen sink URI would end up never satisfying all folks or
use cases. For example, a URI factory;
Uris.RFC1234.create("http://";);
Uris.RFC5678.create("http://";);
Uris.DEFAULT.create("http://";);
This implies an interface defining a URI.
I do not know what the default would be.
Gary
was (Author: garydgregory):
Would we consider supporting different RFCs clearly and separately. I'm
concerned that a kitchen sink URI would end up never satisfying all folks or
use cases. For example, a URI factory;
Uris.RFC1234.create("http://";);
Uris.RFC5678.create("http://";);
Uris.DEFAULT.create("http://";);
I do not know what the default would be.
Gary
> 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]
