Now I’ve changed the IP-address manually in several config files (from Nuxt.js and from Vert.x and in the axios call itself, as it didn’t work with the Nuxt.js config) and got Chrome to work with the self signed certificate again (or better: I disabled all checks)… Access to XMLHttpRequest at '' (redirected from '') from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. So I’d love to get it to work with Chrome first. I’m using docker-compose and I’ve now used the host network, because otherwise I couldn’t get it to work.įirefox is currently not supported by the backend I guess, as I have no OPTIONS routes. No 'Access-Control-Allow-Origin' header is present on the requested resource. Its a CORS issue, your api cannot be accessed directly from remote or different origin, In order to allow other ip address or other origins from accessing you api, you should add the 'Access-Control-Allow-Origin' on the api's header, you can set its value to '' if you want it to be accessible to all, or you can set specific domain or ips like. I have a config file from which the Vert.x Server reads the URL for Keycloak. 52 The Cors Error Seen this before Seeing it right now When working with APIs in your application code, honestly, this bug creeps up more often than it should. When a simple Button is clicked, axios makes a request to the Vert.x backend which says, hey, I’m redirecting you to Keycloak. If you set this into the response header of the requested file, you will allow everyone to access the resources: > Not recommended allow all domains. We are trying to add the CORS header but still getting the error -> No Access-control-allow-origin Header is present on requested resource.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |