an even better approach would be correctly setup your webserver to
send the appropriate expire times for the .m3u8 files so your caches
neither any other one would cache them :)
a correctly expire time for the .ts could be sent as well, allowing
them to be cached
Em 31/01/13 22:19, Scott Baker escreveu:
> I want to make sure that .m3u8 files are *never* cached. Those files are
> updated every 5 seconds on my server, and always have the same name.
> What is the best way to make sure that they are never cached? This is
> what I came up with:
>
> refresh_pattern \.m3u8 0 0% 0
>
> Conversely, MPEG segments are .ts files and are ALWAYS the same. The
> file names roll, so once an mpeg segment is created it will *never* get
> updated. Thus those files should ALWAYS be cached, and there is no
> reason to ever refresh the file. How do I ensure that .ts segments are
> cached, and there is no reason to re-validate them. These pieces of
> content will expire after 15 minutes (it's live video), so there is no
> reason to keep any .ts files that are older than 15 minutes. This is
> what I came up with:
>
> refresh_pattern \.ts 900 100% 900
>
> Currently I'm seeing a lot of TCP_REFRESH_UNMODIFIED in my logs for .ts
> segments. I must be doing something wrong.
>
-- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertrudes_at_solutti.com.br My SPAMTRAP, do not email itReceived on Fri Feb 01 2013 - 00:30:45 MST
This archive was generated by hypermail 2.2.0 : Fri Feb 01 2013 - 12:00:05 MST