You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you can use Rocket to serve static assets such as Images, JS files, etc easily and it works, however if you try to serve video media (and potentially audio, haven't tested audio), it will only work in some browsers, because of browser support and leniency on the Range and RangeByte headers being respected and the correct information being returned.
Currently, it seems to send all bytes at the same time, even if the Range requested was only bytes 0-1 (which is the header request made by Safari to determine media type).
If you return all content back on that request, Chrome and other browsers are happy to play that content and ignore the mistake, however Safari refuses to play the content.
A convincing use-case for this feature.
Using Rocket to serve static movie assets as part of your website is not currently possible, it currently requires either third-party (S3) or alternate server software for serving that asset, which isn't desirable if you want to lock the content behind auth walls etc in your application.
Why this feature can't or shouldn't exist outside of Rocket.
It can exist outside of Rocket, however it makes using Rocket as a static server unusable since a common type of asset is not able to be sent to a popular browser (Mobile safari + Desktop).
The text was updated successfully, but these errors were encountered:
Currently you can use Rocket to serve static assets such as Images, JS files, etc easily and it works, however if you try to serve video media (and potentially audio, haven't tested audio), it will only work in some browsers, because of browser support and leniency on the Range and RangeByte headers being respected and the correct information being returned.
Currently, it seems to send all bytes at the same time, even if the Range requested was only bytes 0-1 (which is the header request made by Safari to determine media type).
If you return all content back on that request, Chrome and other browsers are happy to play that content and ignore the mistake, however Safari refuses to play the content.
Using Rocket to serve static movie assets as part of your website is not currently possible, it currently requires either third-party (S3) or alternate server software for serving that asset, which isn't desirable if you want to lock the content behind auth walls etc in your application.
It can exist outside of Rocket, however it makes using Rocket as a static server unusable since a common type of asset is not able to be sent to a popular browser (Mobile safari + Desktop).
The text was updated successfully, but these errors were encountered: