From 7f6ff825892f1ad62ee6ed2e55eedadf7a016df4 Mon Sep 17 00:00:00 2001
From: Richard Brady <rnbrady@gmail.com>
Date: Mon, 7 Oct 2024 14:35:24 +0100
Subject: [PATCH] Clarifiy that allow_custom_ports flag affects WebSockets.

---
 src/content/compatibility-dates/allow-custom-ports.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/content/compatibility-dates/allow-custom-ports.md b/src/content/compatibility-dates/allow-custom-ports.md
index d230cfc550de7a2..3d71bc660bf3c4c 100644
--- a/src/content/compatibility-dates/allow-custom-ports.md
+++ b/src/content/compatibility-dates/allow-custom-ports.md
@@ -25,3 +25,4 @@ const response = await fetch("https://example.com:8000");
 With allow_custom_ports the above example would fetch `https://example.com:8000` rather than
 `https://example.com:443`.
 
+Note that creating a WebSocket client with a call to `new WebSocket(url)` will also obey this flag.