The following code:
fetch(\'http://localhost:8080/root/1487171054127/k_query_bearer_token\', {
mode: \'no-cors\', credentials: \'include\'
})
Remove mode: 'no-cors'
.
When you use no-cors
mode, you’re explicitly specifying that you want an “opaque response”.
Your script can’t access any properties of an opaque response—instead essentially all you can do is cache it. no-cors
mode is basically useful only when doing caching with Service Workers.
If the reason you have your script using no-cors
mode is because cross-origin requests to the server otherwise won’t work, the right solution is either to update the server-side code to send the Access-Control-Allow-Origin
response header and other CORS headers—if you have access to the server do to that—or else, use a reverse proxy like https://cors-anywhere.herokuapp.com/.