The custom Content-Type header you’re sending causes your request to be preflighted, which means an OPTIONS request, containing some metadata about the POST request that is about to be dispatched, will be sent before the actual POST request. Your server needs to be prepared to deal with this OPTIONS request. You haven’t specified what the … Read more
Using native DOMParser getCurrentCity(location) can be written: function getCurrentCity(location) { const lat = location.coords.latitude; const lon = location.coords.longitude; return fetch(apis.currentWeather.url(lat, lon)) .then(response => response.text()) .then(str => new window.DOMParser().parseFromString(str, “text/xml”)) .then(data => console.log(data)); }
Unfortunately, this cannot be done, as this type of message in the console is printed by chrome itself. Repressing this type of message has been debated for years, but the consensus seems to be that this message is desirable – see this discussion. Just in case you’re interested: As per this comment, the reason we’re … Read more
Like epascarello said, the server that hosts the resource needs to have CORS enabled. What you can do on the client side (and probably what you are thinking of) is set the mode of fetch to CORS (although this is the default setting I believe): fetch(request, {mode: ‘cors’}); However this still requires the server to … Read more
When you say fetch(‘data.json’) you are effectively requesting http://yourdomain.com/data.json since it is relative to the page you’re are making the request from. You should lead with forward slash, which will indicate that the path is relative to the domain root: fetch(‘/js/data.json’). Or fully qualify with your domain fetch(‘http://yourdomain.com/js/data.json’).
A solution without dependencies. Node headers.set(‘Authorization’, ‘Basic ‘ + Buffer.from(username + “:” + password).toString(‘base64’)); Browser headers.set(‘Authorization’, ‘Basic ‘ + btoa(username + “:” + password));
You can make the request through a public CORS proxy; to do that try changing your code to: fetch(‘https://cors-anywhere.herokuapp.com/http://api.deezer.com/search/track/autocomplete?limit=1&q=eminem’) That sends the request through https://cors-anywhere.herokuapp.com, which forwards the request to http://api.deezer.com/search/track/autocomplete?limit=1&q=eminem and then receives the response. The https://cors-anywhere.herokuapp.com backend adds the Access-Control-Allow-Origin header to the response and passes that back to your requesting frontend code. … Read more
I’d suggest a wrapper that checks response.ok which will be true if the response code is 2xx. Note this statement from the MDN page on fetch(): An accurate check for a successful fetch() would include checking that the promise resolved, then checking that the Response.ok property has a value of true. An HTTP status of … Read more
The same-origin policy restricts the kinds of requests that a Web page can send to resources from another origin. In the no-cors mode, the browser is limited to sending “simple” requests — those with safelisted methods and safelisted headers only. To send a cross-origin request with headers like Authorization and X-My-Custom-Header, you have to drop … Read more
You’re getting an opaque response [1] [2], because you’re using fetch with mode: ‘no-cors’. You need to use mode: ‘cors’ and the server needs to send the required CORS headers [3] in order to access the response.