{"id":777,"date":"2021-09-01T14:38:41","date_gmt":"2021-09-01T11:38:41","guid":{"rendered":"https:\/\/plumrocket.com\/learn\/?p=777"},"modified":"2022-10-05T18:01:46","modified_gmt":"2022-10-05T15:01:46","slug":"how-to-configure-magento-2-varnish-in-a-few-clicks","status":"publish","type":"post","link":"https:\/\/plumrocket.com\/learn\/magento-2-varnish-configuration","title":{"rendered":"How to Configure Magento 2 Varnish in a Few Clicks"},"content":{"rendered":"\n

Caching is the main part of any web server. With platforms like Magento 2, it is more important to install the cache for one essential reason. It can drastically reduce the load on your online store and speeds up the page response which improves performance<\/a> and user experience, and enhances sales. Among the variety of cache options on today\u2019s market, Varnish is one of the most popular to consider. So, let\u2019s explore the importance of Magento 2 Varnish and find out the steps of its installation on your store.<\/p>\n\n\n\n

\"How<\/figure><\/div>\n\n\n\n

What is Varnish and How Does It Work with Magento 2 <\/h2>\n\n\n\n

Varnish Cache is an open-source web application accelerator that is designed for content-heavy dynamic websites like Magento 2. Since Varnish is used only with HTTP protocol, it is also known as caching HTTP reverse proxy. However, there is a possibility to configure Varnish with HTTPS protocol with the help of NgniX acting as a proxy.<\/p>\n\n\n\n

If you are running Magento 2, it is essential to know that the platform supports Varnish 4.x and 5.x. Below, you can see a basic view of Varnish in your Magento topology:<\/p>\n\n\n\n

\"Basic<\/figure><\/div>\n\n\n\n

As you can see in the preceding figure, HTTP requests to the webserver result in a number of requests for CSS, HTML, JavaScript, and images. All of them are also called assets. Varnish \u0421ache goes next and passes all requests to the web server.<\/p>\n\n\n\n

Since the web server returns the assets, the cacheable assets are stored in Varnish. Any future requests are fulfilled by Varnish which means the requests no longer reach the server. As a result, Varnish returns the cached content very quickly. Hence, you get a faster response time to return content to visitors and a reduced amount of requests passing straight to Magento 2.<\/p>\n\n\n\n

It is important to remember that assets cached by Varnish either expire automatically at a configurable interval or are replaced by newer versions of the same assets. Also, you can clear the cache manually in 2 different ways:<\/p>\n\n\n\n

1) Using the web interface, follow the path:<\/p>\n\n\n\n

Magento Admin Panel\u2192System\u2192Cache Management<\/strong><\/p>\n\n\n\n

After that, click \u201cFlush Magento Cache\u201d<\/p>\n\n\n\n

2) Using the command line, run the command:<\/p>\n\n\n\n

<\/div>
$ php bin\/magento cache:clean<\/code><\/pre><\/div>\n\n\n\n
Note, Magento<\/a> recommends using Varnish in production since built-in full-page caching is much slower than Varnish Proxy.<\/p>\n\n\n\n
How to Benefit from Magento 2 Varnish as HTTP Processor <\/h2>\n\n\n\n
Varnish includes Varnish Configuration Language (VCL) that is the core configuration mechanism for this cache. It is a domain-specific language (DSL) used for writing hooks. The hooks are called at critical points of request handling.<\/p>\n\n\n\n
Compared to other HTTP caches, VCL makes Varnish more adjustable and configurable. After being loaded, a VCL script is translated to \u0421 and compiled to a shared object by the system compiler. Then it is loaded straight into Varnish that can be configured without a restart.<\/p>\n\n\n\n
Each request passes through Varnish which lets you influence which way the request is handled. All you require is to change the VCL code. To be more specific, you can:<\/p>\n\n\n\n