Skip to content

api: Turn on RFC 3986 parsing by default and update javadoc.#12764

Open
jdcormie wants to merge 1 commit intogrpc:masterfrom
jdcormie:grpc-rfc-3986-enable
Open

api: Turn on RFC 3986 parsing by default and update javadoc.#12764
jdcormie wants to merge 1 commit intogrpc:masterfrom
jdcormie:grpc-rfc-3986-enable

Conversation

@jdcormie
Copy link
Copy Markdown
Member

@jdcormie jdcormie commented Apr 17, 2026

Added discussion of ambiguity which is technically new with the RFC 3986 change. A target like foo:8888 didn't used to be ambiguous (if you believed the javadoc API contract) because it is not a "valid NameResolver-compliant" URI -- the path doesn't start with / and so java.net.URI considers it opaque, not hierarchical as required. Fortunately (???) ManagedChannelImplBuilder never enforced the !isOpaque() requirement mentioned in the javadoc and so this ambiguity isn't actually new in practice. gRPC C++ also appears to suffer from the same problem.

Will not merge until the time is right!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant