CORS errors using cloudfront

nikdow
(@nikdow)

11 months, 4 weeks ago

Upgrade of Jetpack plugin from 14.7 to 14.8 causes CORS errors:

Access to script at ‘https://cdn.spelfabet.com.au/wp-includes/js/dist/script-modules/interactivity/index.min.js?ver=55aebb6e0a16726baffb‘ from origin ‘https://www.spelfabet.com.au‘ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.Understand this error
make-a-referral/:815

GET https://cdn.spelfabet.com.au/wp-includes/js/dist/script-modules/interactivity/index.min.js?ver=55aebb6e0a16726baffb net::ERR_FAILED 200 (OK)Understand this error
make-a-referral/:1 Access to script at ‘https://cdn.spelfabet.com.au/wp-content/www.spelfabet.com.au/plugins/jetpack/jetpack_vendor/automattic/jetpack-forms/dist/modules/form/view.js?ver=14.8‘ from origin ‘https://www.spelfabet.com.au‘ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.Understand this error
make-a-referral/:814

GET https://cdn.spelfabet.com.au/wp-content/www.spelfabet.com.au/plugins/jetpack/jetpack_vendor/automattic/jetpack-forms/dist/modules/form/view.js?ver=14.8 net::ERR_FAILED 200 (OK)Understand this error

I don’t see any Access-Control-Allow-Origin header in the page request using DevTools (Chrome).
Thousands of other scripts are getting loaded from the CDN OK with similar destinations, e.g.
https://cdn.spelfabet.com.au/wp-includes/js/hoverintent-js.min.js?ver=2.2.1
https://cdn.spelfabet.com.au/wp-content/www.spelfabet.com.au/plugins/woocommerce/assets/js/frontend/woocommerce.min.js?ver=9.9.5

The first request that fails has Request Headers:
sec-fetch-mode cors
sec-fetch-site same-site

whereas the requests that are succeeding have request headers:
sec-fetch-mode no-cors
sec-fetch-site same-site

The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)

Thread Starter nikdow
(@nikdow)

11 months, 4 weeks ago

Update: I created a test site, with a separate CDN (that’s a lot of work!)
first I ran it without the CDN plugin and the errors persist with JP 1.48
It loads the scripts because the CORS errors aren’t present when not using a CDN.
The form errors that I’m seeing in https://test.spelfabet.com.au/make-a-referral/ are still present!
So I’m going to mark this issue as resolved since the CDN is not the cause of our issue.

Viewing 1 replies (of 1 total)

The topic ‘CORS errors using cloudfront’ is closed to new replies.