On Wed, Jul 14, 2021 at 8:15 AM Reinis Rozitis <r@roze.lv> wrote:

> > How? The presentation does not cover that.
>
> You shouldn't stick to a single youtube video.
>

This is the only video that I found that covers HLS. I also read the module
documentation.

> And it can't be a simple HTTP
>
> It is.
> Even the name HLS stands for "HTTP Live Streaming".
>
>
> > , because as you said yourself, with HLS I would just end up with a
> cached playlist and bunch of useless VOD chunks that I don't want to ever
> serve.
>
> As with http objects to cache or not to cache is something the server can
> specify (like no-cache headers (add_header 'Cache-Control' 'no-cache'; [1])
> etc) and it's on player/client side to honour those.


OK, if I have an HLS stream with caching turned off, will nginx do the
correct thing? That is, serve the same stream (+/- couple of RTT) to each
user and not cause interruptions of the stream when the chunks roll over?
Because I don't see how that is possible if it is treated as simple HTTP.
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx