Re: Byte-range request not possible for proxy_cache if origin doesn't return accept-ranges header

Hi Lucas, On Wed, Nov 14, 2018 at 06:50:23PM +, Lucas Rolff wrote: > Hi Roman, > > I can confirm that indeed does fix the problem, thanks! > > I do wonder though, why not let nginx make the decision instead of relying on > what the origin sends or does not send? nginx tries to be

Re: Byte-range request not possible for proxy_cache if origin doesn't return accept-ranges header

Hi Roman, I can confirm that indeed does fix the problem, thanks! I do wonder though, why not let nginx make the decision instead of relying on what the origin sends or does not send? Thanks! On 14/11/2018, 17.36, "nginx on behalf of Roman Arutyunyan" wrote: Hi, On Wed, Nov

Re: Byte-range request not possible for proxy_cache if origin doesn't return accept-ranges header

Hi, On Wed, Nov 14, 2018 at 02:36:10PM +, Lucas Rolff wrote: > Hi guys, > > I've been investigating why byte-range requests didn't work for files that > are cached in nginx with proxy_cache, I'd simply do something like: > > $ curl -r 0-1023 https://cdn.domain.com/mymovie.mp4 > > What

Byte-range request not possible for proxy_cache if origin doesn't return accept-ranges header

Hi guys, I've been investigating why byte-range requests didn't work for files that are cached in nginx with proxy_cache, I'd simply do something like: $ curl -r 0-1023 https://cdn.domain.com/mymovie.mp4 What would happen was that the full length of a file would be returned, despite being in