Nginx-0.8.53 segfault

Server NGINX
21

On 1/14/11 1:55 PM, “Maxim D.” [email protected] wrote:

Right now I think correct solution would be to move r->cache into
upstream’s private data (r->upstream). Igor?

FWIW, we are doing some thing with file_cache that are not upstream
based.
I hope to be able to release those soon.

–
Brian A.

22

Thank you guys!
Is there some workaround? Should I disable caching of images produced by
image filter?

23

Maxim, thank you again!

It worked for me.

24

Hello!

On Fri, Jan 14, 2011 at 09:06:28PM +0100, Maxim C. wrote:

Thank you guys!
Is there some workaround?

Using named location in error_page 415 should help, i.e.

location ... {
    ...
    image_filter ...
    error_page 415 = @empty;
}

location @empty {
    empty_gif;
}

Maxim D.

25

Hello!

On Fri, Jan 14, 2011 at 09:55:35PM +0300, Maxim D. wrote:

790 if (c->updated) {

    location / {
    }

    location /bad/ {
        return 404;
    }
}

Right now I think correct solution would be to move r->cache into
upstream’s private data (r->upstream). Igor?

The attached patch moves r->cache into r->upstream (and resolves
the SIGSEGV in question).

To Igor:

The patch is rather big and touches lots of code. I would like to
get some explicit response on it to avoid unneeded merge work.

Maxim D.