Inconsistent handling of IPv6 scope in SocketsHttpHandler's connection pool #135103

Activity

1. MihaZupan

   added this to the 12.0.0 milestone on Oct 2, 2026
2. MihaZupan

   added

   area-System.Net.Http

   on Oct 2, 2026
3. dotnet-policy-service commented on Oct 2, 2026

   

   dotnet-policy-serviceBot

   on Oct 2, 2026 – with Dotnet Policy Service

   Contributor

   More actions

   Tagging subscribers to this area: @karelz, @dotnet/ncl
   See info in area-owners.md if you want to be subscribed.
4. wfurt commented on Oct 2, 2026

   

   wfurt

   on Oct 2, 2026

   Last edited by wfurt

   Member

   More actions

   I'd be in favor. I don't even think it is breaking change. We do use scope for IPAddress.
5. makazeu commented on Oct 10, 2026

   

   makazeu

   on Oct 10, 2026

   Last edited by makazeu

   Contributor

   More actions

   Confirmed on .NET 10.0.12: changing a scoped IPv6 proxy from %1 to %2 still selects %1 in ConnectCallback, even when the first connection attempt failed. This reproduces with HTTP, HTTPS, and SOCKS5 proxies for both HTTP and HTTPS requests.

   A targeted fix can make proxy pool keys scope-sensitive while retaining canonical URI equivalence. Changing Uri.Equals globally should be considered separately because it changes URI-keyed collection behavior.

   Working on a fix for proxy pool keys.

   Note

   This analysis was generated with GitHub Copilot.
6. MihaZupan commented on Oct 11, 2026

   

   MihaZupan

   on Oct 11, 2026

   MemberAuthor

   More actions

   Changing Uri.Equals globally should be considered separately because it changes URI-keyed collection behavior.

   I disagree, I think fixing this in Uri would be cleaner.

   👍React with 👍2Reacted by Tomas Weinfurt and Makazeu
7. makazeu commented on Oct 12, 2026

   

   makazeu

   on Oct 12, 2026

   Last edited by makazeu

   Contributor

   More actions

   9. > Changing Uri.Equals globally should be considered separately because it changes URI-keyed collection behavior.

   I disagree, I think fixing this in Uri would be cleaner.
   

   Working on raising another PR to fix Uri.Equals

   Update:
   PR done: #135617