got it.
i will add an extra header_rewrite for .m3u8
thanks again.
On Sun, Dec 3, 2017 at 10:44 AM, ezko <erez.koler@> wrote:
> Thanks !!!
>
> But can you explain why you used such a large max-age ?
It's just an example.
> When i tried it with your max-age value it didn't work (i kept getting the
> same old playlist and segments).
> So I tried changing max-age to 10 seconds and now it seems to work much
> better.
>
> If my HLS playlist has 3 segments and each segment is 10 second each ,
> then
> why should i cache anything for more then 30 seconds ?
I think there are 2 distinct HLS cases. For live streaming, the
playlist will change frequently (but usually, the encoded segments
won't). For already recorded content, neither likely change. You might
distinguish between the 2 cases in your remap rule. Or, you could add
extra header_rewrite rules like
cond %{CLIENT-URL:PATH} /\.m3u8/
or perhaps look at the mime type like
cond %{HEADER:Content-Type} /mpegURL/
(though, now re-reading, perhaps you only have the live streaming case.)
> For live HLS , since everything is short lived and assuming i only have a
> small number of streams and enough RAM , is there a way to configure ATS
> to
> work with the in-memory cache only ?
No, the ram cache is too intertwined to the disk cache to do that.
miles
--
Sent from: http://apache-traffic-server.24303.n7.nabble.com/
