![]() 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. ![]() CORS header ‘Access-Control-Allow-Origin’ missing - Access-Control-Allow-Origin already given. Is this something I can overcome from the frontend I know for a fact that people use that API so it cant be backend fault, right. If you want to bypass that restriction when fetching the contents with fetch API or XMLHttpRequest in javascript, you can use a proxy server so that it sets the. 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. I keep on getting the same error: CORS header ‘Access-Control-Allow-Origin’ missing. I have a config file from which the Vert.x Server reads the URL for Keycloak. ![]() When a simple Button is clicked, axios makes a request to the Vert.x backend which says, hey, I’m redirecting you to Keycloak. htaccess (just add to the destination site and origin site) Header always set Access-Control-Allow-Origin '' Header always set Access-Control-Allow-Methods 'POST, GET, OPTIONS, DELETE, PUT' Header always set Access-Control-Max-Age '1000' Header always set Access-Control-Allow-Headers 'x-requested-with, Content-Type, origin, authorization, accept, client-security-token. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |