Magento 2 – Varnish Cache-Control: Max_Age 0 Issue

cachemagento2varnish

So I have installed xVarnish or, CacheWall, but the Cache-control max_age is set to 0. I found this post here but I am not sure of the exact location that I can implement the answers suggestion of

"You are just missing session_cache_limiter and session_cache_expire, which should be the first lines executed on the requested PHP script, even before session_start()."

The same person edited their answer to also give the added option of modifying Apache mod_expires which I tried to do with this tutorial here which threw an error of wrong syntax when I tried to restart my apache2 server.

Is there a tutorial some one could point me too? or some direction on modifying the session_start in magento?

Sorry if this has been asked before and for my noobness. The url I am trying this on is www.brotomic.com the headers contain

 [root@host ~]# curl -I http://www.brotomic.com
HTTP/1.1 302 Found
Date: Thu, 17 Aug 2017 18:14:15 GMT
Pragma: no-cache
Cache-Control: max-age=0, must-revalidate, no-cache, no-store
Expires: Wed, 17 Aug 2016 18:14:15 GMT
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Set-Cookie: PHPSESSID=o3h5m3r4ei5o3628ij49940u62; expires=Thu, 17-Aug-2017 19:14:15 GMT; Max-Age=3600; path=/; domain=www.brotomic.com; HttpOnly
Location: http://brotomic.com/?SID=o3h5m3r4ei5o3628ij49940u62
X-UA-Compatible: IE=edge
Content-Length: 0
Content-Type: text/html; charset=UTF-8
X-Varnish: 229728
Age: 0
X-Cache: MISS
Connection: keep-alive

We are running on a dedicated server and also with centOS/cpanel.
Also would a VCL file change be appropriate for this?

Thanks.

Best Answer

I was able to find the session_cache_limiter and session_cache_expire through the WHM dashboard in MultiPHP INI Editor which allowed me to change the settings of these 2 features which changed my header and allowed Varnish to be be enabled.

Related Solutions

Magento – Varnish – Error 503 Backend fetch failed

After compared with the /etc/varnish/default.vcl, I found after removing the .probe section in the backend default can solve this. Still wondering why the probe caused this

backend default {
    .host = "127.0.0.1";
    .port = "8080";
    .first_byte_timeout = 600s;
    .probe = {
        .url = "/pub/health_check.php";
        .timeout = 2s;
        .interval = 5s;
        .window = 10;
        .threshold = 5;
   }
}

backend default {
    .host = "127.0.0.1";
    .port = "8080";
    .first_byte_timeout = 600s;
}

Updated:

Just change the following line:

.url = "/pub/health_check.php";

.url = "/health_check.php";

solved the problem, refer to this article https://www.sohaib.com/magento-2-12-varnish-error-503-backend-fetch-failed-solved-php-7-1-nginx-varnish-5-x/

Magento2 – How to Cache Magento 2 with Varnish

It just feels strange because of Magento and all people that post Tutorials and How To's claim that this should work fine just by setting it up(like FPC used to work).

I will join them :).

Magento 2 and Varnish are compatible out of the box. If something is not working, there was a step missed:

On the teams live projects I see the response cookie of PHPSESSID as well as Magento form key on every single page

If you see it on every page, this likely means that the Magento 2 VCL file was not applied. For reference, you can look at this line.

To recap: Magento 2 does spit out PHPSESSID on every page but Magento 2's VCL unsets it and overrides the built-in VCL in a way that even with cookies, the page can be cached.

Troubleshoot

In proper configuration the Expires and Cache-Control header which is emitted by the Magento 2 app will ensure the TTL to be positive, e.g. 1-day expiration. That is the TTL which Varnish will use to cache the page.

You can verify the headers coming from your backend app via curl. Simply launch the curl against Magento 2 directly. This way you can see headers which Varnish sees.

Sample headers from Magento 2 (before Varnish):

HTTP/1.1 200 OK
Server: nginx
Date: Fri, 02 Mar 2018 14:40:55 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: store=default; expires=Sat, 02-Mar-2019 14:40:55 GMT; Max-Age=31536000; path=/; HttpOnly
Set-Cookie: PHPSESSID=hbtgntuutdaa460hjtfdobbjt3; expires=Fri, 02-Mar-2018 15:40:55 GMT; Max-Age=3600; path=/; domain=www.example.com; secure; HttpOnly
Pragma: cache
Cache-Control: max-age=86400, public, s-maxage=86400
Expires: Sat, 03 Mar 2018 14:40:55 GMT
X-Magento-Tags: store,cms_b,theme_editor_backend_css_block,cms_b_header_cms_links,cms_b_header_cms_content,cms_b_footer_cms_content,cms_p_58,cat_p
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN

There is Set-Cookie which is fine because M2 VCL will take care of it. The Expiress and Cache-Control specify 1 day of TTL for Varnish.

On my clean Magento 2 I can also see that Pragma and Cache-Control do not allow caching of any page.

This is to be expected. Those headers are meant for browsers and do not affect caching by Varnish. They are set by Magento 2 VCL.

Best Answer

Related Solutions

Magento – Varnish – Error 503 Backend fetch failed

Magento2 – How to Cache Magento 2 with Varnish

Troubleshoot

Related Topic