New answers tagged

1

I see that there's a Set-Cookie header in your response. That will cause Varnish to mark this incoming response as uncacheable because it changes the state. If the next request for this resource doesn't return a response that contains the Set-Cookie header, you'll be fine and Varnish will store the object in the cache. If every request returns a Set-Cookie ...


0

Did you manage to get an answer about this, I'm also getting the same issue! running 2.3.5-p2 magento2 enterprise


0

You need to follow Magento 2 devdocs as they told step-to-step setting and configuration of varnish cache. If you have already installed varnish cache on your server then you need to configure Port in the admin of Developer section then you will require to final verification that it's working or not as per the below guideline of Devdoc Magento 2: https://...


0

In order to purge specific objects from cache, the Magento back-end sends HTTP PURGE requests which Varnish would act upon. The problem arises when CloudFlare proxies are enabled, as these proxies silently disregard HTTP PURGE requests, and do NOT proxy them to your host. I believe that by default, Magento will send the HTTP PURGE request to itself on its ...


1

For Magento to perform well, you'll need Redis and Varnish. Redis is a distributed key-value store that is used to cache information coming from the database Varnish is a reverse caching proxy that is used to cache entire pages I wouldn't use Memcached, because it performs the same role as Redis. I'd consider Memcached the predecessor of Redis and Redis ...


Top 50 recent answers are included