Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Playing mp4 videos from a Virtual Path Provider on iPhone/iPads

Vote:
 

Hi Guys,

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.

 

Cheers.

#41186
Jul 06, 2010 15:16
Vote:
 

Same problem here.

Any solution on this one?

#50742
May 11, 2011 13:52
Vote:
 

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).

#50762
May 12, 2011 7:36
Vote:
 

Just for reference. I run into same problem, found a solution by Mark Everard:

http://www.markeverard.com/blog/2011/07/05/serving-videos-to-ios-devices-from-episerver-vpp-folders/

code: http://world.episerver.com/Code/Mark-Everard/FortuneCookieRangeRequestFileHandler/

 

#57908
Apr 03, 2012 11:36
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.