FF153 Range requests pass through SW in same-origin no-cors requests#44580
FF153 Range requests pass through SW in same-origin no-cors requests#44580hamishwillee wants to merge 3 commits into
Conversation
github-actions
Bot
added
Content:Firefox
|
Preview URLs (1 page) Flaws (1) Found an unexpected or unresolvable flaw? Please report it here. URL:
External URLs (1)URL:
(comment last updated: 2026-06-26 05:12:01) |
|
|
||
| - A same-origin fetch request for a media element (for example, from a {{htmlelement("video")}} element) will now pass through a service worker without stripping the {{httpheader("Range")}} header. | ||
| Previously the `Range` header was only preserved in same-origin CORS requests, made by adding the `crossorigin` attribute (`<video crossorigin>`). | ||
| Note that fetch requests for genuinely cross-origin media don't yet go through service workers. |
There was a problem hiding this comment.
@jakearchibald I decided to add a release note following your comment in https://bugzilla.mozilla.org/show_bug.cgi?id=1465074#c34 . This look OK to you?
Note that I took your comment about cross origin media literally (it is possibly you meant cross origin no-cors media goes through the SW but range headers are stripped - but I doubt it)
|
I'm sorry for the flip flopping on this, but I'd recommend against landing this. There was a WHATNOT meeting last night where folks suggested the behaviour here may change in the near future, to what Firefox was doing before this change. So, Firefox may switch back to the previous behaviour pretty soon. Again, sorry about the flip-flopping on it. |
3 participants
FF153 allows
Rangeheaders to be preseved in a same-origin no-cors requests passed through a service worker.This is not hugely interesting, but has been added to the release note for historical record.
Related docs work can be tracked in #44467