lao8n / cnstlltn

MIT License
0 stars 0 forks source link

CORS resource header problem #20

Closed lao8n closed 10 months ago

lao8n commented 10 months ago

Access to internal resource at 'https://accounts.google.com/o/oauth2/v2/auth?response_type=code&client_id=194094976957-s4uccitb516kkvcra1brbbe40398i6rl.apps.googleusercontent.com&redirect_uri=https%3A%2F%2Fca-web-4a73yskoiju2e.whiteground-d98c7a61.eastus.azurecontainerapps.io%2F.auth%2Flogin%2Fgoogle%2Fcallback&scope=openid+profile+email&state=redir%3D%252Fmanifest.json%26nonce%3Dc41961ec8636466bb3c0bd568c14509f_20230829190553' (redirected from 'https://ca-web-4a73yskoiju2e.whiteground-d98c7a61.eastus.azurecontainerapps.io/manifest.json') from origin 'https://ca-web-4a73yskoiju2e.whiteground-d98c7a61.eastus.azurecontainerapps.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

lao8n commented 10 months ago

this is only a problem if i include withCredentials = true in the axios user service stuff.. if i remove it this is not a problem