Files over HTTP do not support 206 Partial Content

[diachedelic]

HTML5 <audio> and <video> elements make use of Range requests to estimate media duration, and facilitate seeking. It appears that Capacitor's file server, at least on Android, does not support the Range header on requests:

GET http://localhost/_capacitor_file_/storage/emulated/0/Documents/1553226944608.webm
Range: bytes=0-

HTTP/1.1 200 OK
Content-Length: 124870
Content-Type: video/webm
Cache-Control: no-cache
Client-Via: shouldInterceptRequest

Along with serving correct Content-Type headers, I feel this feature is necessary for streaming media from the filesystem.

[diachedelic]

I see that there is support for 206 responses in some capacity, am I just doing something wrong?

[jcesarmobile]

Looking at the code, the Range is only checked for the app assets (public folder), not to downloaded files, will fix it.

[llorenspujol]

Range request are not working correctly in my case, actually I may do something wrong, but it only fails using the capacitor server... I opened this issue explaining the use case.

Is quite annoying since I can't put sound in my app... well... I can maybe play the first 3 seconds of the audio 🤣 , just kidding, but any help would be really appreciated :) !