varnish giving error 503

[Pablo J. Villarruel]

Sorry but, the last week I have the same issue, I can fix it add feature
probe over the zone backend Config.
El mar 11, 2013 6:42 p.m., "Per Buer" <perbu at varnish-software.com> escribió:

> Hi,
>
> On Mon, Mar 11, 2013 at 4:02 PM, Mike Franon <kongfranon at gmail.com> wrote:
>
>> Hi,
>>
>> I am trying to get varnish up and running super fast for a production
>> website, we are hammered.
>>
>> We only want to cache one URL, that is being hammered, and pass
>> everything else through, I know this is a just a simple config, but is
>> there anything I am missing to get a 503?  Is it because our servers
>> are being hammered that it is not even able to get pages to cache?
>>
>
> I'm guessing your clients are sending Cookie headers to Varnish and
> Varnish isn't able to cache. Instead of forcing a lookup, which is a bad
> idea, you should try to unset the Cookie header and let the default logic
> handle it. You're already doing this with the response headers so you are
> half way.
>
>
> --
>  <http://www.varnish-software.com/> *Per Buer*
> CEO | Varnish Software AS
> Phone: +47 958 39 117 | Skype: per.buer
> We Make Websites Fly!
>
>
> _______________________________________________
> 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/20130311/66d19d30/attachment.html>