Hmm, issue with this change is that now all the DelegatingHandler wrappers run for WebSocket requests, which is a problem in the AccessTokenHttpMessageHandler case when running in WASM due to headers not being settable. Not sure if the header would just be ignored, but regardless, the access token factory would be called again which would be unnecessary, unless we changed the handler to detect a WebSocket request and removed the access token factory call from WebSocketsTransport.

How hard is it now to force HTTP/1.1 for all requests to get the old behavior if you really want to?

In order to force HTTP/1.1 on all requests now (if for some reason ALPN negotiation isn't gracefully falling back to HTTP/1.1 or some other reason), you can write the following code:

private class Http11Handler : DelegatingHandler
{
    public Http11Handler(HttpMessageHandler handler)
        : base(handler)
    { }

    protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        request.Version = HttpVersion.Version11;
        return base.SendAsync(request, cancellationToken);
    }
}

HubConnection CreateConnection()
{
    return new HubConnectionBuilder().WithUrl(url, options =>
    {
        options.HttpMessageHandlerFactory = handler =>
        {
            return new Http11Handler((HttpClientHandler)handler);
        };
    }).Build();
}

@BrennanConroy, this change will be considered for inclusion in the blog post for the release it'll ship in. Nice work!

Please ensure that the original comment in this thread contains a clear explanation of what the change does, why it's important (what problem does it solve?), and, if relevant, include things like code samples and/or performance numbers.

This content may not be exactly what goes into the blog post, but it will help the team putting together the announcement.

Thanks!

@adityamandaleeka Additional testing added. Approve and merge at will 😃

Thanks @BrennanConroy!