You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Default install in developer mode with Varnish enabled and configured properly. Browser cache disabled
Steps to reproduce
Load a page in the browser and ensure Varnish cache has cached static assets like .css, .js
Run bin/magento cache:clean full_page
Load the same page as step 1 and observe the cache behavior on static assets
Expected result
Static assets would have a Varnish cache miss due to full_page cache being previously cleared
Actual result
Static assets are cache hits. (Non-static assets cleared properly.)
Due to the existing VCL section on purging, static assets can't be purged using the Magento application. Only resources with the X-Magento-Tags-Pattern header will ever be purged by the existing conditional. Static assets will never have this header.
Preconditions
Default install in developer mode with Varnish enabled and configured properly. Browser cache disabled
Steps to reproduce
bin/magento cache:clean full_page
Expected result
Static assets would have a Varnish cache miss due to full_page cache being previously cleared
Actual result
Static assets are cache hits. (Non-static assets cleared properly.)
Due to the existing VCL section on purging, static assets can't be purged using the Magento application. Only resources with the
X-Magento-Tags-Pattern
header will ever be purged by the existing conditional. Static assets will never have this header.Recommend adding something that clears all cached resources when a "purge all" request is made by Magento.
The text was updated successfully, but these errors were encountered: