Add separate WS and WSS ports for browser refresh server to fix TLS port conflict

[Copilot]

Fix dotnet watch port binding when DOTNET_WATCH_AUTO_RELOAD_WS_PORT is set with TLS

Changes:

• Revert previous change that only bound HTTPS
• Add new environment variable DOTNET_WATCH_AUTO_RELOAD_WSS_PORT
• Add BrowserWebSocketSecurePort property to EnvironmentOptions
• Update BrowserRefreshServer to accept and use both ports
• Update WebApplicationAppModel to pass the new parameter
• Rename properties from AutoReloadWebSocket* to BrowserWebSocket*
• Test the fix manually with separate ports
• Run existing tests to ensure no regressions

Original prompt

---

This section details on the original issue you should resolve

<issue_title>dotnet watch fails when DOTNET_WATCH_AUTO_RELOAD_WS_PORT is set and TLS is supported (binds http and https to same port)</issue_title>
<issue_description>### Describe the bug

When DOTNET_WATCH_AUTO_RELOAD_WS_PORT is set to a fixed value and TLS is supported, dotnet watch fails during startup with an Address already in use exception.

The failure is caused by the browser refresh server attempting to bind both http and https endpoints to the same host and port, which results in a port conflict even when the port is otherwise free.

Unsetting the environment variable allows dotnet watch to start successfully, but the port is then randomly assigned.

To Reproduce

1. Create a new Blazor project:

dotnet new blazor -o BlazorSample
cd BlazorSample

2. Ensure HTTPS dev certs are available:

dotnet dev-certs https --check

3. Set a fixed WS port:

$env:DOTNET_WATCH_AUTO_RELOAD_WS_PORT=8081

4. Run:

dotnet watch

Expected behavior

dotnet watch starts successfully and binds the browser refresh WebSocket server to the specified port.

Actual behavior

dotnet watch ❌ An unexpected error occurred: System.IO.IOException: Failed to bind to address http://127.0.0.1:8081: address already in use.
 ---> Microsoft.AspNetCore.Connections.AddressInUseException: Only one usage of each socket address (protocol/network address/port) is normally permitted.
 ---> System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportOptions.CreateDefaultBoundListenSocket(EndPoint endpoint)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()m.Net.Sockets.SocketException (10048)

Further technical details

When TLS is supported, the browser refresh server configures Kestrel with:

builder.UseUrls($"https://{hostName}:{port}", $"http://{hostName}:{port}");

This attempts to bind both HTTP and HTTPS to the same host and port, which results in an AddressInUse error.

Relevant references:

• Environment variable definition:
  https://github.com/dotnet/sdk/blob/main/src/BuiltInTools/Watch/Context/EnvironmentVariables.cs#L58-L60
• Browser refresh server binding logic:
  https://github.com/dotnet/sdk/blob/main/src/BuiltInTools/HotReloadClient/Web/BrowserRefreshServer.cs#L56-L63
• PR introducing the environment variable:
  Dotnet watch browser refresh configurable port #50629
  </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes dotnet watch fails when DOTNET_WATCH_AUTO_RELOAD_WS_PORT is set and TLS is supported (binds http and https to same port) #52908

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[dbreshears]

@copilot, please revert the last change, what is needed is 2 Environment variables. DOTNET_WATCH_AUTO_RELOAD_WS_PORT and a new one DOTNET_WATCH_AUTO_RELOAD_WSS_PORT with variables for AutoReloadWSPort and AutoReloadWSSPort. Then in FromEnvironment we need AutoReloadWebSocketSecurePort set to AutoReloadWSSPort

[Copilot]

@copilot, please revert the last change, what is needed is 2 Environment variables. DOTNET_WATCH_AUTO_RELOAD_WS_PORT and a new one DOTNET_WATCH_AUTO_RELOAD_WSS_PORT with variables for AutoReloadWSPo...

Done! I've implemented the two environment variables approach:

• Added DOTNET_WATCH_AUTO_RELOAD_WSS_PORT environment variable in EnvironmentVariables.cs
• Added AutoReloadWebSocketSecurePort property to EnvironmentOptions and wired it up in FromEnvironment()
• Updated BrowserRefreshServer to accept both ports and use them separately for HTTP and HTTPS

Users can now set:

export DOTNET_WATCH_AUTO_RELOAD_WS_PORT=8081
export DOTNET_WATCH_AUTO_RELOAD_WSS_PORT=8082
dotnet watch

Tested and verified both ports are used correctly. Commit: 813585f

[Copilot]

Pull request overview

This PR fixes a port binding conflict in dotnet watch when DOTNET_WATCH_AUTO_RELOAD_WS_PORT is set with TLS support enabled. Previously, the browser refresh server attempted to bind both HTTP and HTTPS endpoints to the same port, causing an "address already in use" error. The fix introduces a new environment variable DOTNET_WATCH_AUTO_RELOAD_WSS_PORT to allow separate configuration of WebSocket ports for HTTP and HTTPS connections.

Changes:

• Adds DOTNET_WATCH_AUTO_RELOAD_WSS_PORT environment variable for HTTPS WebSocket port configuration
• Renames internal properties from AutoReloadWebSocket* to BrowserWebSocket* for better clarity
• Updates browser refresh server to use separate ports for HTTP and HTTPS when TLS is supported

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/BuiltInTools/Watch/Context/EnvironmentVariables.cs	Adds AutoReloadWSSPort property to read the new HTTPS port environment variable
src/BuiltInTools/Watch/Context/EnvironmentOptions.cs	Renames WebSocket-related properties and adds BrowserWebSocketSecurePort property
src/BuiltInTools/Watch/AppModels/WebApplicationAppModel.cs	Updates parameter names and passes the new secure port to BrowserRefreshServer
src/BuiltInTools/HotReloadClient/Web/BrowserRefreshServer.cs	Accepts secure port parameter and uses it for HTTPS endpoint binding

[Copilot]

This change introduces a new environment variable and modifies the browser refresh server's port binding behavior, but there are no new tests to verify this functionality. Consider adding a test that verifies when both DOTNET_WATCH_AUTO_RELOAD_WS_PORT and DOTNET_WATCH_AUTO_RELOAD_WSS_PORT are set with TLS enabled, the HTTP and HTTPS endpoints bind to their respective ports correctly.

[tmat]

Superseded by #53108