Handling HTML5 Video for iOS and Safari clients

[Guillaume Quintard]

Don't pipe. ever. Unless your are using websockets.

do_stream is set by default, you can remove it.

Are we talking aboud VoD or Live? if the latter, remember to set grace to
0, other you'll have outdated manifest problems.

What isn't working on Safari? Does the problem goes away if you connect
straight to the origin? (ie. no varnish) What do the developer tools tell
you? Have you looked at varnishlog?

-- 
Guillaume Quintard

On Fri, Jul 21, 2017 at 12:27 AM, Leon <info+varnish at shee.org> wrote:

> Branch: varnish-5.1.2
> Config: mostly default
>
> Dear List,
>
> there are a lot of stuff in the results of common search engines concerning
> streaming mp4 files via varnish. But my mental picture is still unsharp.
> Therefore
> following questions; It seems that Safari-Browser has still a problem with
> such
> assets. I had tried two approaches:
>
> 1st: Just "pass" it to the backend:
>
>  vcl_recv : if ( req.url ~ "\.(mp4|webm)$" ) { return(pipe); }
>
> or
>
> 2nd: Deliver it directly
>
>  vcl_recv             : if ( req.url ~ "\.(mp4|webm)$" ) { unset
> req.http.cookie; }
>  vcl_backend_response : if ( bereq.url ~ "\.(mp4|webm)$" ) { set
> beresp.do_stream = true; }
>
>
> Both don't help to get the Safari browser to display the video content as
> done by the Firefox browser for example.
>
>
> So, the questions:
>
> Which one should be the preferential approach - in general to deliver mp4
> files?
>
> Does someone has the same issues with the Safari-Browser? What could help
> here?
>
> In the mean time, any other suggestions would be greatly appreciated.
>
> Thanks,
> Leon
>
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170721/26c673c9/attachment-0001.html>