dotnet/runtime

HTTP/2 extended connect error message doesn't blame the server

Open

#111,470 opened on 2025年1月15日

GitHub で見る
 (9 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
area-System.Net.Httphelp wanted

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (平均マージ 12d 11h) (30d で 661 merged PRs)

説明

Description

System.Net.Http.HttpRequestException: Failed to establish web socket connection over HTTP/2 because extended CONNECT is not supported. Try to downgrade the request version to HTTP/1.1.

Reproduction Steps

Conect to a websocket with Extended Connect

Expected behavior

Work?

Actual behavior

Exception

Regression?

No response

Known Workarounds

No response

Configuration

   conection = new ClientWebSocket();

   conection.Options.SetRequestHeader("Stream-Type", ",mystream");
   conection.Options.HttpVersion = HttpVersion.Version30;

   await conection.ConnectAsync(new Uri(webSocketUri), Net.client, CancellationToken.None);

Other information

No response

コントリビューターガイド