fix port error when fallback to http

[dameng324]

As discussed in previous PR: #43620,

I pass the original registryName to FallbackToHttpMessageHandler and check it if contains a port or not. If not, set the uriBuilder.Port = -1.

For summary. It should behave like this:

• If user set an insecure registry without port, It will fallback to http default port 80.
• If user set an insecure registry with a port, even 443(the default port of https), It will maintain the orginal port.

Fixed: #43618 , dotnet/sdk-container-builds#588

[baronfel]

Thanks for the rebase - this seems very clear. Do you have any idea how this could be tested via unit tests? Maybe via the pattern that @tmds did for this auth handler PR - a mock HttpHandler?

[baronfel]

Thanks for adding the tests!

[dameng324]

@baronfel the work is done,can you spare some time to check?

[baronfel]

This LGTM, thanks @dameng324! I kicked CI to see if those two failing legs can get green. If so, we'll merge and I'll backport the fix to 8.0.400 and 9.0.100 and work on getting approval for those.

[baronfel]

/backport to release/8.0.4xx

[baronfel]

/backport to release/9.0.1xx

[github-actions]

Started backporting to release/8.0.4xx: https://github.com/dotnet/sdk/actions/runs/11370820390

[github-actions]

Started backporting to release/9.0.1xx: https://github.com/dotnet/sdk/actions/runs/11370821680