Varnish 500's now not 302's

[Andreas Plesner Jacobsen]

On Fri, May 11, 2012 at 09:30:52AM +1100, Nicholas_Maesepp at scee.net wrote:

> I guess technically I realize this is from the cache, my question is more 
> along the lines of what could be causing my objects in the cache to become 
> stop being delivered as is and having a 500 error returned. Is my cache 
> being corrupted in some way when varnish starts to max out the malloc'ed 
> RAM? Seems like a bug to me but can't pinpoint exactly what causes it, 
> just that it happens after X amount of time to any of my instances.

Then you misunderstood me. The 500 is a cached object that your backend served
at the time. You can avoid caching such objects by inspecting the HTTP response
in vcl_fetch and setting TTL and/or using hit for pass and/or saint mode.

It's almost certainly not a bug.

-- 
Andreas