Bobcares

Purge varnish cache – How we do it

by | Nov 5, 2019

Looking for a method to purge Varnish cache?

Varnish cache is useful to speed up websites and reduce the load on the website servers.

However, when the website has new contents, showing the cached results can be a headache

At Bobcares, we receive requests regarding varnish cache as a part of our Server Management Services.

Today, let’s see how our Support Engineers clear varnish cache.

 

What is Varnish Cache?

Basically, Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy.

Varnish Cache is really fast and speeds up website delivery depending on the server architecture.

One of the key features of Varnish Cache is the flexibility of its configuration language, VCL.

A purge takes place when we pick an object from the cache and discard it.

 

How to purge Varnish cache

Recently one of our customers contacted us to purge his Varnish. He had updated the website contents and wanted Varnish to notify Varnish. With the presence of cached content, visitors will still see the old website.

Let us discuss the different methods used by our Support Engineers to clear the cache.

 

1. Using Varnish restart

To clear Varnish cache, we just restart Varnish. This will clear the entire varnish cache in the server. We use the command

service varnish restart

It is the quickest way to purge the entire cache.

 

2. Purge using VCL

To purge a specific object from the cache we need to add a function into VCL.  We add the following contents in the Varnish configuration file. The default Varnish configuration file is at location /etc/varnish/default.vcl.

acl purge {
"localhost";
"1xx.1xx.5x.0"/24;
}
sub vcl_recv {
# allow PURGE from localhost and 1xx.1xx.5x.0

if (req.method == "PURGE") {
if (!client.ip ~ purge) {
return(synth(405,"Not allowed."));
}
return (purge);
}
}

We add the details and save the file.

We can purge varnish cache for a specific URL using CURL.

curl -X PURGE URL-to-PURGE

Example:

curl -X PURGE http://www.domain.com/

 

3. Using the command line

Similarly, we can purge the cache from the command line as well.

The command to purge all varnish cache,

varnishadm 'ban req.url ~ .'

To purge a particular domain or particular URL

varnishadm -T 127.0.0.1:6082 -S /etc/varnish/secret "ban req.http.host ~ www.domain.com && req.url http://www.domain.com"

Again, to purge all .html pages from cache from a domain

varnishadm -T 127.0.0.1:6082 -S /etc/varnish/secret "ban req.http.host ~ www.domain.com && req.url .html"

 

[Trouble in purging Varnish cache? Our Expert Engineers are available 24×7.]

 

Conclusion

In short, we have discussed the methods to purge Varnish cache. Also, we have discussed how our Support Engineers purge varnish cache and help users see the updated website content.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF