Clarify the value of ConnectionInfo.RemoteIpAddress for HTTP/3 over QUIC/UDP
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 290
Description
### Discussed in https://github.com/dotnet/aspnetcore/discussions/68219
Originally posted by **scharnyw** August 5, 2026
The documentation for [`ConnectionInfo.RemoteIpAddress`](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.connectioninfo.remoteipaddress?view=aspnetcore-10.0) states that:
> The result is null if the connection isn't a TCP connection, e.g., a Unix Domain Socket or a transport that isn't TCP based.
But how about HTTP/3 over QUIC/UDP? The server should still be able to get the remote IP and port. If so, the documentation likely needs to be updated.
Contributor guide
Research direction
Start with the ConnectionInfo.RemoteIpAddress API documentation and the linked discussion #68219. Verify the documented behavior for HTTP/3 over QUIC/UDP, then clarify the API documentation so its nullability and remote endpoint behavior are accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100