I'm running into an issue with the Virtual Path Provider where if I upload a mp4 video, I can't play the video back on a iPhone or iPad since it uses byte-range to be able to jump different parts of the system. I know I can put the file in a static directory/folder but this makes it difficult for content editors to upload new content. Is there virtual file provider which will allow both uploading files via the CMS and allow them to be accessed in a static way to allow the use of byte-ranges.
Same problem here.
Any solution on this one?
The file is not delivered to the client directly from the VirtualPathProvider but from a httpHandler. In case for static files from EPiServer virtualpath providers the handler is typically configured to EPiServer.Web.StaticFileHandler. The EPiServer.Web.StaticFileHandler typically uses HttpResponse.TransmitFile to deliver the file to the client.
You could either try to change the httpHandler (under location element for your vpp, e.g. PageFiles) to System.Web.StaticFileHandler (a disadvantage of that is that you loose control over cache headers) or you can write your own httpHandler (e.g. by subclassing EPiServer.Web.StaticFileHandler).
Just for reference. I run into same problem, found a solution by Mark Everard: