WebSocketTransport in Javascript/typescript client did not include headers set using IHttpConnectionOptions

[goyaltushar92]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When we create a signalR connection with headers, like

var connection = new signalR.HubConnectionBuilder()
      .withUrl(hubUrl, {headers: { xyz: 'asd' }}).withAutomaticReconnect()
      .build();
connection.start();

I observed, headers set using options, is missing from some calls when using WebSocketTransport also access_token is in query instead of headers.

Expected Behavior

• Any custom header described by options should be there
• Auth token should use headers

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[BrennanConroy]

That's expected:
https://learn.microsoft.com/javascript/api/%40microsoft/signalr/ihttpconnectionoptions?view=signalr-js-latest#@microsoft-signalr-ihttpconnectionoptions-headers

Note, setting headers in the browser will not work for WebSockets or the ServerSentEvents stream.

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.