Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: d4107fcb3662e705b8f3cf03b7a28a6b9d2682b8
https://github.com/WebKit/WebKit/commit/d4107fcb3662e705b8f3cf03b7a28a6b9d2682b8
Author: Anne van Kesteren <[email protected]>
Date: 2026-09-11 (Fri, 11 Sep 2026)
Changed paths:
M
LayoutTests/imported/w3c/web-platform-tests/cors/cors-safelisted-request-header.any-expected.txt
M
LayoutTests/imported/w3c/web-platform-tests/cors/cors-safelisted-request-header.any.js
M
LayoutTests/imported/w3c/web-platform-tests/cors/cors-safelisted-request-header.any.worker-expected.txt
M
LayoutTests/imported/w3c/web-platform-tests/fetch/range/blob.any-expected.txt
M LayoutTests/imported/w3c/web-platform-tests/fetch/range/blob.any.js
M
LayoutTests/imported/w3c/web-platform-tests/fetch/range/blob.any.worker-expected.txt
M Source/WebCore/platform/network/HTTPParsers.cpp
Log Message:
-----------
Make parseRange() follow the Fetch Standard
https://bugs.webkit.org/show_bug.cgi?id=322999
Reviewed by Youenn Fablet.
261968@main made parseRange() shared between blob: URLs and the CORS-safelisted
request-header check, but it had a few minor issues:
* "bytes" was matched case-insensitively.
* Byte positions were parsed with parseInteger(), which allows a leading "+",
whereas the algorithm collects ASCII digits.
* parseInteger() skips U+000B and U+000C as whitespace.
Apart from addressing those we also make the algorithm perform a single pass as
per the FIXME.
Tests are upstreamed via https://github.com/web-platform-tests/wpt/pull/62329.
Firefox passes all. Chrome passes all CORS tests, but does not reuse the parser
for blob: URLs. Hopefully the new tests will help them address that.
Canonical link: https://commits.webkit.org/320912@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
