You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Turns out, it was incorrectly configured, and HTTP 400 was returned, but since it does not have CORS headers, Firefox devtools indicated the CORS errors in a way that it was grabbing attention more than the 400 error.
I would still recommend sending CORS headers with HTTP errors, to not confuse CORS error with the real error.
notramo
changed the title
CORS error causes 0 visitors recorded
Send CORS header with non-200 HTTP statuses too
May 10, 2024
Describe the Bug
api-gateway.umami.dev
does not return anAccess-Control-Allow-Origin
header.Database
Umami Cloud
Relevant log output
Which Umami version are you using? (if relevant)
Umami Cloud
Which browser are you using? (if relevant)
Firefox
How are you deploying your application? (if relevant)
Umami Cloud
The text was updated successfully, but these errors were encountered: