I ran into an interesting tidbit just now while trying to dynamically stream a video file using a custom http handler. The idea here is to bypass the static handler for a file so that I can perform authentication/preprocessing/etc when a user requests a video resource and I don’t have to expose a static folder with potentially sensitive resources.
I had everything working fine on my desktop browser, but when I went to test on my iPhone I got the dreaded play button with a circle crossed out
I hate that thing.
Anyways, streaming a file from the static handler worked fine though, so what was the difference? This is where I pulled out charles and checked the response headers.
From the static handler I’d get this:
HTTP/1.1 200 OK Content-Type video/mp4 Last-Modified Wed, 15 May 2013 20:59:30 GMT Accept-Ranges bytes ETag "9077fe17af51ce1:0" Server Microsoft-IIS/7.5 X-Powered-By ASP.NET Date Wed, 15… Read more