From 724c2902a13e5a0243c2288d63d4a503440c5914 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 13 Oct 2025 16:40:27 +0000 Subject: [PATCH 1/3] Initial plan From c80254854a34e4d63aa4a05c97fd4594447f9970 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 13 Oct 2025 16:44:33 +0000 Subject: [PATCH 2/3] Update Firefox HTTP/2 WebSocket documentation across all versions Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> --- aspnetcore/fundamentals/websockets.md | 4 ++-- aspnetcore/fundamentals/websockets/includes/websockets7.md | 2 +- aspnetcore/fundamentals/websockets/includes/websockets8.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/aspnetcore/fundamentals/websockets.md b/aspnetcore/fundamentals/websockets.md index a65fea5df19a..e3d500e43bb9 100644 --- a/aspnetcore/fundamentals/websockets.md +++ b/aspnetcore/fundamentals/websockets.md @@ -5,7 +5,7 @@ description: Learn how to get started with WebSockets in ASP.NET Core. monikerRange: '>= aspnetcore-3.1' ms.author: wpickett ms.custom: mvc -ms.date: 07/09/2025 +ms.date: 10/13/2025 uid: fundamentals/websockets --- # WebSockets support in ASP.NET Core @@ -33,7 +33,7 @@ These supported features are available in Kestrel on all HTTP/2 enabled platform > HTTP/2 WebSockets use CONNECT requests rather than GET, so your own routes and controllers may need updating. > For more information, see [Add HTTP/2 WebSockets support for existing controllers](#add-http2-websockets-support-for-existing-controllers) in this article. > -> Chrome and Edge have HTTP/2 WebSockets enabled by default, and you can enable it in FireFox on the `about:config` page with the `network.http.spdy.websockets` flag. +> Chrome, Edge, and Firefox have HTTP/2 WebSockets enabled by default. If you need to manually configure this setting in Firefox, it can be found in the `about:config` page with the `network.http.http2.websockets` flag. WebSockets were originally designed for HTTP/1.1 but have since been adapted to work over HTTP/2. ([RFC 8441](https://www.rfc-editor.org/rfc/rfc8441)) diff --git a/aspnetcore/fundamentals/websockets/includes/websockets7.md b/aspnetcore/fundamentals/websockets/includes/websockets7.md index de7bf43d57c2..6f5731f950d8 100644 --- a/aspnetcore/fundamentals/websockets/includes/websockets7.md +++ b/aspnetcore/fundamentals/websockets/includes/websockets7.md @@ -19,7 +19,7 @@ These supported features are available in Kestrel on all HTTP/2 enabled platform > HTTP/2 WebSockets use CONNECT requests rather than GET, so your own routes and controllers may need updating. > For more information, see [Add HTTP/2 WebSockets support for existing controllers](#add-http2-websockets-support-for-existing-controllers) in this article. > -> Chrome and Edge have HTTP/2 WebSockets enabled by default, and you can enable it in FireFox on the `about:config` page with the `network.http.spdy.websockets` flag. +> Chrome, Edge, and Firefox have HTTP/2 WebSockets enabled by default. If you need to manually configure this setting in Firefox, it can be found in the `about:config` page with the `network.http.http2.websockets` flag. WebSockets were originally designed for HTTP/1.1 but have since been adapted to work over HTTP/2. ([RFC 8441](https://www.rfc-editor.org/rfc/rfc8441)) diff --git a/aspnetcore/fundamentals/websockets/includes/websockets8.md b/aspnetcore/fundamentals/websockets/includes/websockets8.md index 74b287139c90..c09599a23a46 100644 --- a/aspnetcore/fundamentals/websockets/includes/websockets8.md +++ b/aspnetcore/fundamentals/websockets/includes/websockets8.md @@ -19,7 +19,7 @@ These supported features are available in Kestrel on all HTTP/2 enabled platform > HTTP/2 WebSockets use CONNECT requests rather than GET, so your own routes and controllers may need updating. > For more information, see [Add HTTP/2 WebSockets support for existing controllers](#add-http2-websockets-support-for-existing-controllers) in this article. > -> Chrome and Edge have HTTP/2 WebSockets enabled by default, and you can enable it in FireFox on the `about:config` page with the `network.http.spdy.websockets` flag. +> Chrome, Edge, and Firefox have HTTP/2 WebSockets enabled by default. If you need to manually configure this setting in Firefox, it can be found in the `about:config` page with the `network.http.http2.websockets` flag. WebSockets were originally designed for HTTP/1.1 but have since been adapted to work over HTTP/2. ([RFC 8441](https://www.rfc-editor.org/rfc/rfc8441)) From fd9d9803a67dc730c02dc8c0e10b62172b862490 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 13 Oct 2025 17:00:39 +0000 Subject: [PATCH 3/3] Clarify Firefox version 128+ requirement for HTTP/2 WebSockets Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> --- aspnetcore/fundamentals/websockets.md | 2 +- aspnetcore/fundamentals/websockets/includes/websockets7.md | 2 +- aspnetcore/fundamentals/websockets/includes/websockets8.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/aspnetcore/fundamentals/websockets.md b/aspnetcore/fundamentals/websockets.md index e3d500e43bb9..b8f1ee86e4ca 100644 --- a/aspnetcore/fundamentals/websockets.md +++ b/aspnetcore/fundamentals/websockets.md @@ -33,7 +33,7 @@ These supported features are available in Kestrel on all HTTP/2 enabled platform > HTTP/2 WebSockets use CONNECT requests rather than GET, so your own routes and controllers may need updating. > For more information, see [Add HTTP/2 WebSockets support for existing controllers](#add-http2-websockets-support-for-existing-controllers) in this article. > -> Chrome, Edge, and Firefox have HTTP/2 WebSockets enabled by default. If you need to manually configure this setting in Firefox, it can be found in the `about:config` page with the `network.http.http2.websockets` flag. +> Chrome, Edge, and Firefox (version 128 and later) have HTTP/2 WebSockets enabled by default. You can verify or change this setting in Firefox by opening `about:config` and locating the `network.http.http2.websockets` preference. WebSockets were originally designed for HTTP/1.1 but have since been adapted to work over HTTP/2. ([RFC 8441](https://www.rfc-editor.org/rfc/rfc8441)) diff --git a/aspnetcore/fundamentals/websockets/includes/websockets7.md b/aspnetcore/fundamentals/websockets/includes/websockets7.md index 6f5731f950d8..145ff8caa844 100644 --- a/aspnetcore/fundamentals/websockets/includes/websockets7.md +++ b/aspnetcore/fundamentals/websockets/includes/websockets7.md @@ -19,7 +19,7 @@ These supported features are available in Kestrel on all HTTP/2 enabled platform > HTTP/2 WebSockets use CONNECT requests rather than GET, so your own routes and controllers may need updating. > For more information, see [Add HTTP/2 WebSockets support for existing controllers](#add-http2-websockets-support-for-existing-controllers) in this article. > -> Chrome, Edge, and Firefox have HTTP/2 WebSockets enabled by default. If you need to manually configure this setting in Firefox, it can be found in the `about:config` page with the `network.http.http2.websockets` flag. +> Chrome, Edge, and Firefox (version 128 and later) have HTTP/2 WebSockets enabled by default. You can verify or change this setting in Firefox by opening `about:config` and locating the `network.http.http2.websockets` preference. WebSockets were originally designed for HTTP/1.1 but have since been adapted to work over HTTP/2. ([RFC 8441](https://www.rfc-editor.org/rfc/rfc8441)) diff --git a/aspnetcore/fundamentals/websockets/includes/websockets8.md b/aspnetcore/fundamentals/websockets/includes/websockets8.md index c09599a23a46..900a4e8013f2 100644 --- a/aspnetcore/fundamentals/websockets/includes/websockets8.md +++ b/aspnetcore/fundamentals/websockets/includes/websockets8.md @@ -19,7 +19,7 @@ These supported features are available in Kestrel on all HTTP/2 enabled platform > HTTP/2 WebSockets use CONNECT requests rather than GET, so your own routes and controllers may need updating. > For more information, see [Add HTTP/2 WebSockets support for existing controllers](#add-http2-websockets-support-for-existing-controllers) in this article. > -> Chrome, Edge, and Firefox have HTTP/2 WebSockets enabled by default. If you need to manually configure this setting in Firefox, it can be found in the `about:config` page with the `network.http.http2.websockets` flag. +> Chrome, Edge, and Firefox (version 128 and later) have HTTP/2 WebSockets enabled by default. You can verify or change this setting in Firefox by opening `about:config` and locating the `network.http.http2.websockets` preference. WebSockets were originally designed for HTTP/1.1 but have since been adapted to work over HTTP/2. ([RFC 8441](https://www.rfc-editor.org/rfc/rfc8441))