I have no idea what these errors are, nor do I know how to fix it. I’ve tried looking these up on the Mozilla website, and they said it’s a HTTP connection failed at the network or protocol level error…The weird thing is, this did not happen 2 days ago. And 2 days ago, nothing was changed. I’ve tried loading up the page history from 2 days ago, but the same thing happened again.
Have a read about CORS here:
https://support.wix.com/en/article/corvid-accessing-third-party-services-with-the-fetch-api
https://www.wix.com/corvid/forum/community-discussion/problem-with-access-control-allow-origin
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors
https://stackoverflow.com/questions/24371734/firefox-cross-origin-request-blocked-despite-headers
https://github.com/EFForg/https-everywhere/issues/5148
Thanks @givemeawhisky, but I don’t have any of those CORS related things in my code…I’ve never used fetch or anything like that. Is this a cause for concern?
I can’t see clearly the screenshot you pasted, but I’ve also noticed some CORS errors lately, on different Wix’s websites (not only mine).
And it’s an issue on Wix’s side, not ours.
It seems to be related to the lodash.min.js.
Hi @tgkhang262 . Do you have any technical issues correlating with these warnings? Please let me know if you see something. Meanwhile, I’ll check with our developers, if this is something that needs special treatment. Thank you
@aleksander-denga , I don’t know if what I’m going to describe is what Shiro referred to, but anyway, I think you should know about it, as it’s a general issue and not limited to a certain site.
Description:
When the page loads, it throws an error: Access to fetch at 'https://static.parastorage.com/unpkg/lodash@4.17.11/lodash.min.js' from origin 'https://www.{{domain}}' has been blocked by CORS policy: Request header field x-reveal is not allowed by Access-Control-Allow-Headers in preflight response.'
In these cases, it may log to the console: CDN name fetch failed TypeError: Failed to fetch
I don’t know if it has any other effect except for the error itself.
Steps to reproduce: just reload a page many times (it happens once in a while on page loading).
Thank you
@tgkhang262 Hi. I would like to ask you if you still able to reproduce this issue? If so, please share a link to your website and give us more details with steps to reproduce and information about your OS and Browser version.
@jonatandor35 Thank you for your details. I was able to see those warnings, but I think it is a different case and again - it shouldn’t affect functionality of your site. This looks more like internal system stuff. Anyway, I asked our developers to check as well.
@aleksander-denga No, I think the problem is magically fixed, unless that was you guys doing your thing, to which I’ll say thank you very much.
Good that the issue is fixed for you, however i have had a quick read of this and thought I would just post about it here too.
https://www.wix.com/corvid/reference/wix-fetch.html#fetch
Certain CORS (Cross-Origin Resource Sharing) requests are restricted when originating from a browser. Usually, GET requests and certain POST requests can be made from your site’s Public , Page , or Site code. All other requests need to be made from your site’s Backend code. If you are experiencing an issue with a fetch() call due to a CORS restriction, move the fetch() call to the backend as described in Accessing 3rd Party Services .