-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
grpc: add optional interface to return channel authority #5360
Comments
Sure, thanks! Let's name the interface: package resolver
// AuthorityOverrider is implemented by Builders that wish to override the
// default authority for the ClientConn. By default, the authority used is
// target.Endpoint().
type AuthorityOverrider interface {
// OverrideAuthority returns the authority to use for a ClientConn with the
// given target. It must not perform I/O or other blocking operaitons.
OverrideAuthority(target Target) string
} And I think the only real motivation for this feature is to move this special case into the function to be implemented by the unix resolver's builder: Lines 1990 to 1993 in e14d583
Around here: grpc-go/internal/resolver/unix/unix.go Line 60 in e14d583
Which would also be a pretty good test for this functionality in practice. One thing we need to decide is: do we do the |
This issue is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed. |
WIP, adding comment to prevent issue being closed |
This issue is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed. |
Did we make a decision on this one? Thanks. |
hi @easwars, the PR doesn't include percent-encoding and expects it from the name resolver currently |
This is one of the items mentioned in #4717 which did not get done. The below description has been copied over verbatim from #4717. Java and C already support this.
:authority
from the target URI must be the responsibility of the name resolver. See: HTTP2 authority header is not set to resolver.Address.ServerName (?) #4516:authority
pseudo-header, andserverName
for TLS handshake by default.authority
set.The text was updated successfully, but these errors were encountered: