Thanks for your help, removing the bypass solved this issue for me. This
feature request would simplify such configurations:
http://forum.nginx.org/read.php?2,258604
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255421,258617#msg-258617
___
Hello!
On Mon, May 04, 2015 at 07:52:46AM -0400, philipp wrote:
> Hi Maxim,
> should this solution work?
> http://syshero.org/post/49594172838/avoid-caching-0-byte-files-on-nginx
>
> I have created a simple test setup like:
>
> map $upstream_http_content_length $flag_cache_empty {
> default 0
Hi Maxim,
should this solution work?
http://syshero.org/post/49594172838/avoid-caching-0-byte-files-on-nginx
I have created a simple test setup like:
map $upstream_http_content_length $flag_cache_empty {
default 0;
0 1;
}
server {
listen 127.0.0.1:80;
server_name local;
Hello!
On Thu, Dec 11, 2014 at 03:54:25AM -0500, Cord Beermann wrote:
> Hello,
>
> Due to issues with a backend beyond my influence i need to fix this with
> Nginx.
>
> Root-Cause: A CMS generates empty files on a filesystem which will be later
> filled with content. However: those files are th
On the 'Serving Nginx' I'd use Lua to test for a zero byte file and return
the 404 there.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255421,255422#msg-255422
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo
Hello,
Due to issues with a backend beyond my influence i need to fix this with
Nginx.
Root-Cause: A CMS generates empty files on a filesystem which will be later
filled with content. However: those files are there for some time with 0
bytes
and will be served with 200 through a chain of a cachin
