Fix incorrect local and remote address when using domain socket in abstract namespace #5096
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: #5080
Motivation:
ServiceRequestContext.localAddress()
andServiceRequestContext.remoteAddress()
currently returns anInetSocketAddress(0.0.0.0:1)
for domain sockets in abstract namespace.Modifications:
ChannelUtil
to use the parent channel's local address forserver-side domain socket channels to retrieve their socket addresses
reliably
<unknown>
toHttpServerHandler.UNKNOWN_ADDR
so that it's less confusing
Result:
ServiceRequestContext
now returns the correct socket addresses whenthe request is being served via a domain socket in abstract namespace.
(unknown address) arises again.