Self hosted signalr - TLS 1.3 problem

[skibos]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Hi.

I have problem with package @microsoft/signalr client for javascript -> https://www.npmjs.com/package/@microsoft/signalr
I use latest version 8.0.7.

My API is deployed on Azure and I set up self hosted signalR server on Kestrel. Problem exists during trying establishing connection with hub when we have minimum TLS version set to 1.3 on Azure.

Problem:

Websockets doesnt work, long pooling works.

When we change TLS version to 1.2 on Azure then it starts working.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[BrennanConroy]

Azure and I set up self hosted signalR server on Kestrel

Deployed how? Is it in Azure App Service. Linux or Windows? If Windows, that would be using IIS not Kestrel, unless you're using OutOfProcess. Are you using a browser or Node?

TLS with WebSockets shouldn't behave differently from other HTTP requests so this is very odd.