Repository navigation
Serve byte ranges for the homepage video (Safari/iOS) - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Workers static assets ignore Range and always return 200 with the whole file; Safari and iPhone browsers won't play an mp4 served that way. A thin wrapper around the OpenNext worker (web/custom-worker.ts) answers Range requests for /video/* with 206/416, and assets.run_worker_first sends only /video/* through it. Tested on wrangler dev: bytes=0-1, open-ended, suffix, past-end (416), no Range (200), missing file (404), homepage and other assets unchanged, sliced bytes match the file.
🤖 Generated with Claude Code