Bug #88205
openMissing FAL support for byte-range requests
0%
Description
This issue occurs when serving video files from a non publicly accessible FileStorage.\TYPO3\CMS\Core\Resource\ResourceStorage::getPublicUrl()
will generate an URL like this:
/index.php?eID=dumpFile&t=f&f=11623&token=047550942c914f1c4e4ae8d22a0bc2102661019b
When serving video files via a publicly accessible FileStorage the FAL can use "normal" URL, e.g.:
/fileadmin/user_upload/videos/awesome.mp4
iOS devices will check if the server supports byte-range requests when downloading/streaming video files, please have look into the documentation:
https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/CreatingVideoforSafarioniPhone/CreatingVideoforSafarioniPhone.html#//apple_ref/doc/uid/TP40006514-SW6
Normal Web-Servers (like Apache and nginx) usually don't have any issues with byte-range requests.
Unfortunately the FAL can't handle byte-range requests.
I'll suggest that this feature/bug will be handled in \TYPO3\CMS\Core\Resource\ResourceStorage::dumpFileContents()
.
I'm not sure if this is the proper place for that.
I could reconstruct this issue in TYPO3 CMS 8 and 9 (other versions haven't been tested yet).
Updated by Frans Saris about 5 years ago
Would be great if you could bring this to the core.
For the extension fal_securedownload we added this ourselves for now, see https://github.com/beechit/fal_securedownload/blob/5de03db72df85cb78574efe6c823876d2c4539cf/Classes/Hooks/FileDumpHook.php#L193
Updated by Stefan Bürk 8 months ago
- Related to Feature #83145: Add HTTP_RANGE support to the FileDumpController added
Updated by Stefan Bürk 8 months ago
That's not a but. If at all, it's a "missing" feature.
However, added #83145 as related which targets on the same topic in some way.