Varnish 500's now not 302's

[Hugues Alary]

At this point, sending your configuration file would maybe be a good idea.
On May 11, 2012 1:41 AM, "Andreas Plesner Jacobsen" <apj at mutt.dk> wrote:

> 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
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20120511/3726e597/attachment.html>