feat: Allow exposing Cache-Tags header when Varnish serve API and N…

…uxt responses

config/packages/nelmio_cors.yaml

@@ -3,8 +3,8 @@ nelmio_cors:
         origin_regex: true
         allow_origin: ['%env(CORS_ALLOW_ORIGIN)%']
         allow_methods: ['GET', 'OPTIONS', 'POST', 'PUT']
-        allow_headers: ['Content-Type', 'Authorization', 'Www-Authenticate', 'x-g-recaptcha-response']
-        expose_headers: ['Link', 'Www-Authenticate']
+        allow_headers: ['Content-Type', 'Authorization', 'Www-Authenticate', 'x-g-recaptcha-response', 'Cache-Tags']
+        expose_headers: ['Link', 'Www-Authenticate', 'Cache-Tags']
         max_age: 3600
     paths:
         '^/': ~

docker/varnish/default.vcl

@@ -195,9 +195,9 @@ sub vcl_deliver {
     #
     # You can do accounting or modifying the final object here.
 
-    # Remove cache-tags, unless you want Cloudflare or other to see them
+    # Remove cache-tags, unless you want Cloudflare or Nuxt to see them (to use cache tags on Nuxt responses)
+    # Make sure to allow CORS on Cache-Tags header if you want to use it on Nuxt.
     unset resp.http.X-Cache-Tags;
-    # Comment the following line to send the "Cache-Tags" header to the client (e.g. to use CloudFlare cache tags)
     unset resp.http.Cache-Tags;
 }