Re: [whatwg/fetch] Define opaque-response blocking (updated) (PR #1755) from Simon Pieters on 2026-11-03 (public-webapps-github@w3.org from November 2026)

From: Simon Pieters <notifications@github.com>
Date: Tue, 03 Nov 2026 07:30:32 -0800
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Push <push@noreply.github.com>
Message-ID: <whatwg/fetch/pull/1755/before/ef602a86fb4f74cc5fef78e5aedf563451d29a34/after/22>

@zcorpan pushed 4 commits.

8ad6f24c8545aef50673ab4bc5cd791c073051a4  Define opaque-response blocking
b33dd426092afc221ded7928a0058ed243d36b73  Filter opaque ping responses rather than checking them
1b3207d5415ee228a9c810906181c755a21fa78d  Filter opaque beacon responses rather than checking them
2201c4088c2f4829b66dc1816939a3972d784a6a  Fix errors in opaque-response blocking

-- 
View it on GitHub:
https://github.com/whatwg/fetch/pull/1755/changes/ef602a86fb4f74cc5fef78e5aedf563451d29a34..2201c4088c2f4829b66dc1816939a3972d784a6a
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1755/before/ef602a86fb4f74cc5fef78e5aedf563451d29a34/after/22>

Received on Tuesday, 3 November 2026 15:30:38 UTC