500 response with HIT status and cached file is with 200 status

Sat Aug 6 12:45:09 UTC 2016

Hello!

On Thu, Aug 04, 2016 at 11:45:49AM -0300, Wandenberg Peixoto wrote:

> I'm with a weird situation on an nginx instance.
> The object on the cache was stored with 200 OK status, but sometimes when a
> client request this same object nginx log something like 500 as status, HIT
> as cache status, 0 bytes sent and 0 ms as response time.
> 
> Have any of you seen an error like that?
> What may be causing this situation?

This can happen, e.g., due to a memory allocation error.

> Where I can look for more information?

Try looking into the error log for details.

-- 
Maxim Dounin
http://nginx.org/