- #Safari silverlight download mp4
- #Safari silverlight download android
- #Safari silverlight download download
In this case, the video is about 19M, but we only return 2 bytes (byte 0 through byte 1). The response header should indicate that there are only 2 bytes in the body, and specify the overall length of the video: Cache-Control: public, no-cache="Set-Cookie", max-age=3600 In my observations using Fiddler, when given a HTML5 element, iOS Safari will always make the first request for the first two bytes using the Range header in the request: Range: bytes=0-1 I believe this is what allows IIS to break up the file into chunks if the request asks for only particular parts of the file.
The reason that Blob Cache is needed for iOS Safari, I believe, is not because Blob Cache keeps a cache, per se, but more because Blob Cache persists the video to a file so that the request always gets it from the file instead of directly from the database. I believe this could be as low as 0 and still enable iOS Safari video playback. It instructs the browser how long to cache the content before requesting an update. The value you put here is in seconds (so 3600 = 1 hour) and will show up in a “Cache-Control” header in the response along with the video content (I show this in the response header further below). The max-age is not mentioned in the default entry in the web.config. The maxSize is in GB and that is for the entire cache on for this web application on this WFE. The primary notes here are that the location should be on a drive that is different than where the SharePoint ULS logs go to reduce contention.
#Safari silverlight download mp4
By default the Blob Cache XML in the web.config looks like: įor our purposes, we only cared about mp4 video files, so to reduce the impact of our change, the web.config changes look like:
You turn on Blob Cache by updating the web.config files for your web application(s). Along the way, I learned a little more that I thought I would share (for you TL DR folks, stop here)… Blob Cache That’s pretty much the message I wanted to tell because I didn’t see anyone else mentioning it. Since our environment wasn’t live yet, we didn’t need all WFEs to be configured (or so I thought). Note that it is not necessary to enable it on SharePoint application servers- just WFEs. The short answer is that you have to enable Blob Cache on all web front ends.
#Safari silverlight download download
On the video playback page, I would get the Silverlight download logo and link instead (not what I wanted). You see, I did enable Blob Cache for the single SharePoint web front end that my client browsers were using (we didn’t have load balancing turned on for this environment yet), but the video still failed to show on the iPhone and iOS. I found this to be the case, but wanted to write this post to clarify just a little. They seem to require everything to be just a certain way for things to work.Īfter a little digging, I found blog posts that mentioned that I needed to enable Blob Cache for SharePoint. I had recalled from past projects that Safari on an iPhone and iPad are very unforgiving.
#Safari silverlight download android
Everything was working fine except that the videos wouldn’t play on an iPhone or iPad even though they worked on an Android and Windows Phones. We used the Video content type that stores the video and related information (such as the thumbnail image) within a document set, and I created a custom hover capability similar to how it works on a search results page.
I recently needed to provide video playback capability for a client running SharePoint 2013 within Azure.
0 kommentar(er)
