Skip to content

Update Firefox HTTP/2 WebSocket documentation - enabled by default in version 128+ with renamed config preference #36212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 13, 2025
Merged

Update Firefox HTTP/2 WebSocket documentation - enabled by default in version 128+ with renamed config preference #36212

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
724c290
Initial plan
Copilot Oct 13, 2025
c802548
Update Firefox HTTP/2 WebSocket documentation across all versions
Copilot Oct 13, 2025
fd9d980
Clarify Firefox version 128+ requirement for HTTP/2 WebSockets
Copilot Oct 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions aspnetcore/fundamentals/websockets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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 (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))

Expand Down
2 changes: 1 addition & 1 deletion aspnetcore/fundamentals/websockets/includes/websockets7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 (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))

Expand Down
2 changes: 1 addition & 1 deletion aspnetcore/fundamentals/websockets/includes/websockets8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 (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))

Expand Down