Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: d955a8125a72bbab7e59684882ea03078b0748d9
https://github.com/WebKit/WebKit/commit/d955a8125a72bbab7e59684882ea03078b0748d9
Author: Youenn Fablet <[email protected]>
Date: 2026-09-03 (Thu, 03 Sep 2026)
Changed paths:
M
LayoutTests/imported/w3c/web-platform-tests/fetch/range/non-matching-range-response-expected.txt
M
LayoutTests/imported/w3c/web-platform-tests/fetch/range/resources/video-with-range.py
Log Message:
-----------
WPT fetch/range/non-matching-range-response.html subtest is failing
rdar://186542248
https://bugs.webkit.org/show_bug.cgi?id=323290
Reviewed by Anne van Kesteren.
fetch/range/non-matching-range-response.html is using
fetch/range/resources/video-with-range.py to serve media requests.
This server can in one case answer range requests with a 200 response, but the
response body would only contain the bytes specified by the range request.
This is inconsistent as a server answering a range request with 200 should
ignore the requested range.
Cocoa WebKit media engine is making a first request with a byte 0-1 range.
A 200 response containing only two bytes is served and the media load fails as
there is not enough data.
We fix this by changing the server so that, should it answers a range request
with a 200 response, it provides the whole media content as the response body.
*
LayoutTests/imported/w3c/web-platform-tests/fetch/range/non-matching-range-response-expected.txt:
*
LayoutTests/imported/w3c/web-platform-tests/fetch/range/resources/video-with-range.py:
(main):
Canonical link: https://commits.webkit.org/320414@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
