I'm experiencing CORS issues with axios inside Custom Components after updating to Chrome 142. Setting Access-Control-Allow-Private-Network to disabled resolves it, but is there a way to fix this without disabling it?
Thank you for flagging this.
This appears to be due to the local network access restrictions that they have rolled out in the most recent 149 chrome release. It looks like there is a clearer breakdown of what this means and how to work around it here.
It says that the user should be given a permission prompt - is that happening here? Otherwise setting the Access-Control-Allow-Private-Network in your Chrome settings seems to be the fix here.
For Chrome enterprise users there does seem to be a cleaner option where you can add url allow lists for local network requests.
1 Like