Re: [whatwg/fetch] Define opaque-response blocking (updated) (PR #1755)

@zcorpan pushed 6 commits.

fdbbfdbffe5a3bf6f59041de13aabed490c9d5e2  Tie subsequent media requests to URLs that sniffed as audio or video
1c925458a297e28e2f615c124efc43a604bc5894  Read the first bytes of a response from a clone of its body
b3065cadb2ddee6e332fe95a0985d75dd730830d  Fix the JavaScript and JSON check in opaque-response blocking
3227c7c5c88f4a1b17d3f1e91f20d56df2a00239  Replace the Content-Range grammar with a parser
1405a51a8a23f9cd18d5ed0fddb7bab60157dea1  Check redirect responses that won't be followed
5d29ca402b8207d7c1167189764948a8c998d1da  Editorial: tidy up opaque-response blocking

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

Message ID: <whatwg/fetch/pull/1755/before/aea658627142aaf025fa8707855b2c3e797160cb/after/5d>

Received on Friday, 6 November 2026 08:10:10 UTC