HI there...
Is anyone using the full page cache addon? I was excited when I saw the team had developed a custom varnish implementation as I was thinking about doing this myself. I have hit the odd stumbling block, but in general, it seems to be installing ok and generating the correct VCL file which is activated in Varnish.
However, one thing I don't get about the code for the addon is this array:
'disable_for_extensions' => array(
'jpg', 'jpeg', 'png', 'gif', 'ico', 'tiff', 'tif', 'bmp', 'ppm', 'pgm', 'xcf', 'psd', 'webp', 'svg',
'css', 'js',
'html', 'txt',
'woff', 'eot', 'otf', 'ttf',
'zip', 'sql', 'tar', 'gz', 'tgz', 'bzip2', 'mp3', 'mp4', 'flv', 'ogg', 'swf',
),
This code is in app/addons/full_page_cache/schemas/full_page_cache/varnish.php
Basically this array is used to tell the varnish VCL file which files to ignore from the cache. Basically this list rules out most of the files used on any website. Which I don't understand. For example. My product pages use the .html extension and they are immediately excluded from the cache.
Maybe I don't quite understand their approach, but it seems wrong to me. If I make this an empty array and reactivate the addon then the page is cached and when its cached, it loads so much faster - I can't wait to get this running on my site.
I just want to understand their approach before I modify this file.
Cheers,
Nathan