nginx is too strict about accept-ranges

Hi I am using nginx to proxy/cache requests from different origin servers, some of which I don't have access to (can't change their behaviour). Recently I stumbled upon a problem where nginx wouldn't serve partial objects (even after they are cached) although upstream server would happily do that.

Re: Problem with big files

Hi Justin Justin Dorfman Wrote: --- > > > > I use a patch > > Maxim provided some time ago allowing range requests to receive HTTP > 206 if > > a resource is not in cache but it's determined to be cacheable... > > > Can you please link to this

Problem with big files

Hi Recently I hit quite big problem with huge files. Nginx is a cache fronting an origin which serves huge files (several GB). Clients use mostly range requests (often to get parts towards the end of the file) and I use a patch Maxim provided some time ago allowing range requests to receive HTTP 2

Age header support

Hi Is Age header support on a roadmap for the forseeable future? I am mainly looking at the upstream side (and I saw there was a discussion in the developer zone a few months back) but it would be great to have full-blown support. Regards, Kuba Posted at Nginx Forum: http://forum.nginx.org/read

Re: ngx_slab_alloc() failed: no memory in cache keys zone "zone-xyz"

> It does so - if an allocation of a cache node fails, this will > trigger a forced expiration of a cache node, and then tries to > allocate a node again. This is more an emergency mechanism > though (and not guaranteed to work, as another allocation may > fail, too), hence alerts are logged i

Re: ngx_slab_alloc() failed: no memory in cache keys zone "zone-xyz"

> What currently can be used for such a use case is "inactive=" > parameter of the proxy_cache_path directive (see > http://nginx.org/r/proxy_cache_path). It ensures that items not > recently requested are removed from the cache, including ones > created with proxy_cache_min_uses. Have you tr

Re: ngx_slab_alloc() failed: no memory in cache keys zone "zone-xyz"

Hi Maxim Let me explain the use case. I am using cache module to serve very large library. Some files are very popular but a ot of them are not popular at all though. To deal with this long tail I use proxy_cache_min_uses to cache only after it was requested several times. So what I think happens

Re: ngx_slab_alloc() failed: no memory in cache keys zone "zone-xyz"

Hi I am struggling with the very same issue at the moment... If I read the right the code correctly all that nginx cares about is cache size, keys zone size is not checked at all (except when more space needs to be allocated). ngx_http_file_cache_manager(void *data) { // if (size < cach