Purge specific object, not all variants

Hi, Theoretical question. Supposedly I want to introduce Vary: by device classification: mobile / desktop (via devicedetect etc.) How would I go around purging just the specific variant of an object, i.e. purge a page for mobile only? The documentation here:

Re: Log slow backend requests. VSL-query?

Thank you very much, Geoff. > On 21 Mar 2017, at 21:28, Geoff Simmons <ge...@uplex.de> wrote: > > On 03/21/2017 07:11 PM, Danila Vershinin wrote: >> >> Trying to log only the slow backend requests: >> >> varnishncsa -b -q 'Timestamp:Process[2] >

Log slow backend requests. VSL-query?

Hello, Trying to log only the slow backend requests: varnishncsa -b -q 'Timestamp:Process[2] > 0.1’ does not produce any output. In fact, even varnishncsa -b -q 'Timestamp:Process[2] > 0’ does not work. What am I doing wrong? :)___ varnish-misc

Re: Server requirements for installing Varnish

Those are for building / compiling Varnish on your server. If you’re installing Varnish from its official repository, you don’t need any extras. > autoconf > automake > jemalloc-devel > libedit-devel > libtool > ncurses-devel > pcre-devel > pkgconfig > python-docutils > python-sphinx > graphviz

Re: Varnishlog. Get entries by XID

Thanks much, Geoff. Best Regards, Danila > On 10 Apr 2017, at 16:36, Geoff Simmons <ge...@uplex.de> wrote: > > On 04/10/2017 03:18 PM, Danila Vershinin wrote: >> >> Say I have stumbled upon a "Backend Fetch Failed” page and that >> gives me an XID. &

Re: Python 2.7

Hi, There’s existing Varnish 5.1.1 + CentOS 6 build by @ingvar here: https://copr.fedorainfracloud.org/coprs/ingvar/varnish51/ If you need your own I guess you can expand on the .spec file (can be freely extracted from SRPM file of

Varnishlog. Get entries by XID

Hi, Say I have stumbled upon a "Backend Fetch Failed” page and that gives me an XID. How do I easily query varnishlog for corresponding client and backend requests? varnishlog -q “XID = 12345” doesn’t work ___ varnish-misc mailing list

Softpurge and nearly immediate refresh?

Hi, What I work with: * Grace mode configured to be 60 seconds when backend is healthy * Using softpurge module to adjust TTL to 0 upon PURGE. The whole idea is increasing chances that visitors will get cached page after cache was PURGEd for a page. Standard piece: sub vcl_hit { if

Re: Softpurge and nearly immediate refresh?

Hi Guillaume, This should absolutely work. Thank you :) Best Regards, Danila > On 9 Apr 2018, at 12:18, Guillaume Quintard > wrote: > > You can purge then set the method to GET then restart. Would that work for > you? signature.asc Description: Message

Re: Softpurge and nearly immediate refresh?

h a new object. > > -- > Guillaume Quintard > >> On Sat, Apr 7, 2018 at 12:10 PM, Danila Vershinin <cia...@gmail.com> wrote: >> Hi, >> >> What I work with: >> >> * Grace mode configured to be 60 seconds when backend is healthy >> * U

Re: Softpurge and nearly immediate refresh?

Ah, I’m using Varnish 4.1, guess might have to look into >= 5.2. Thanks! :) Best Regards, Danila > On 12 Apr 2018, at 12:25, Guillaume Quintard <guilla...@varnish-software.com> > wrote: > > bereq.is_bgfetch? > > -- > Guillaume Quintard > > On Thu, Apr 1

Re: Softpurge and nearly immediate refresh?

ou to man vcl :-)) > > -- > Guillaume Quintard > > On Wed, Apr 11, 2018, 22:39 Danila Vershinin <cia...@gmail.com > <mailto:cia...@gmail.com>> wrote: > So I guess I’m looking into having one background fetch trigger another > background fetch (to sequentially refresh d

Re: Softpurge and nearly immediate refresh?

arnish-software.com>> wrote: > >> Hi, >> >> You can purge then set the method to GET then restart. Would that work for >> you? >> >> Other way is to use req.hash_always_miss that will only revalidate if we are >> able to fetch a new object. >

Re: Varnish error for failed backend

t 14:25, Geoff Simmons <ge...@uplex.de> wrote: > > On 03/31/2018 10:21 AM, Danila Vershinin wrote: >> >> If a constant PHP error occurs in the backend and there is no cache - >> we see Backend fetch failed. > [...] > >> ... it always take

Varnish error for failed backend

Hi, I have configured Varnish backend probes + grace mode. Works great. One thing I’d like to address with this setup (this is Magento website, but this “issue” applies to other website types) is more relevant error pages. If a constant PHP error occurs in the backend and there is no cache -

Serve cached object without assembling ESI?

Hi, I'm trying to understand whether it's feasible to build a CDN of Varnish instances, whose primary origin(backend) is a Varnish instance which processes an ESI-capable app. So basically: USA visitor -> Varnish USA -> Varnish primary -> THE APP with ESI blocks RUS visitor -> Varnish RUS ->

Re: Serve cached object without assembling ESI?

set resp.do_esi = false; > } > } > > Should be fairly straightforward. > > Cheers, > > -- > Guillaume Quintard > > >> On Sun, Sep 15, 2019 at 12:19 AM Danila Vershinin wrote: >> Hi, >> >> I'm trying to understand whether it's feasi

Re: Varnish : Varnish not loading CSS and JS.

Hi, I don't think it's related to Varnish. 1. You should not be using pub/ in your URLs. The secure Magento 2 setup assumes that pub/ directory is your web root, so you should end up with URLs without it. 2. Your CSS/JS is not loaded because they are returning 404s (thus text/html MIME type,

Re: Varnish : Varnish not loading CSS and JS.

nish also the path remains same, and I get the > CSS and JS. What changes would you recommend? Thank you. :-) > On 09/10/19 4:06 AM, Danila Vershinin wrote: > > Hi, > > I don't think it's related to Varnish. > > 1. You should not be using pub/ in your URLs. The secure Magento 2 s