-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse server does not support range #6244
Comments
Parse Server recently improved byte range support. #6028 What file adapter are you using? Also does .mov files work for you in safari? |
Well, try the cURL command on a .mp4, it doesn’t work.
I don’t set a file adapter, so the default one. I believe safari only uses the “Range: 0-1“ header on MP4 files (uses “Range: 0-“ like other browsers on other file types) so it probably does work then, but I need it working for mp4. Don’t quote me on that though. Thanks for the quick reply! |
This was an issue with using the default file adapter (storing directly in db). Switching over to AWS bucket fixed it. Not entirely sure why. |
Issue Description
Accessing a file on parse server on safari doesn't work due to Range header not being supported.
Steps to reproduce
Using cURL:
curl --range 0-100 http://localhost:3000/parse/files/path/to/file.mp4 -o test.mp4
. As you can see, this doesn't work, however, if you do--range 0-
which most browsers do (but not safari, they do 0-1), it works.Expected Results
For video to be returned.
Actual Outcome
Get a corrupt file.
Environment Setup
Server
Database
Logs/Trace
None.
The text was updated successfully, but these errors were encountered: