No caching is set at all on S3. I've edited theS3 Cors:
With no difference. I think this is more for accessing the font from the s3 bucket, whereas, in my case, the font is being accessed by the S3 Bucket from the Bitnami Wordpress Lightsail stack.
I'm still noticing the form doesn't load at all, with Header set Access-Control-Allow-Origin "*". Since the form does load without that, is there a way to just add the cors configuration to only the folder where the font comes from?
This is what I get when I don't include your cors in the .conf file:
Access to font at 'https://hub.swanthorne.io/wp-content/plugins/formidable/fonts/s11-fp.ttf?v=7' from origin 'https://s3.eu-west-2.amazonaws.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
hub.swanthorne.io/wp-content/plugins/formidable/fonts/s11-fp.ttf?v=7:1 GET htt..://hub.swanthorne.io/wp-content/plugins/formidable/fonts/s11-fp.ttf?v=7 net::ERR_FAILED
leave-a-review.html?&frm_page=5:1 Access to font at 'https://hub.swanthorne.io/wp-content/plugins/formidable/fonts/s11-fp.woff?v=7' from origin 'https://s3.eu-west-2.amazonaws.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
hub.swanthorne.io/wp-content/plugins/formidable/fonts/s11-fp.woff?v=7:1 GET htt..://hub.swanthorne.io/wp-content/plugins/formidable/fonts/s11-fp.woff?v=7 net::ERR_FAILED
So can the Access-Control-Allow-Origin be added only to https://hub.swanthorne.io/wp-content/plugins/formidable/fonts?
Using your method, even if I change the wildcard for the site address, it doubles up for some unknown reason;
eg. Access to XMLHttpRequest at https://hub.swanthorne.io/wp-json/frm/v2/forms/2?return=html from origin https://s3.eu-west-2.amazonaws.com has been blocked by CORS policy:
The 'Access-Control-Allow-Origin' header contains multiple values 'https://s3.eu-west-2.amazonaws.com, htt..://s3.eu-west-2.amazonaws.com', but only one is allowed.