Closed
Bug 1115151
Opened 10 years ago
Closed 7 years ago
CORS: better message in console for mismatches
Categories
(DevTools :: Console, defect)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1475391
People
(Reporter: mkohler, Unassigned)
References
Details
I used Access-Control-Allow-Origin with a wildcard and the credentials flag set, because I didn't know better.
Firefox just told me that the request was blocked, but not why.
in Google Chrome I got this: A wildcard '*' cannot be used in the 'Access-Control-Allow-Origin' header when the credentials flag is true. Origin 'http://localhost:8080' is therefore not allowed access.
These kind of errors should have better messages to explain to the user what exactly went wrong.
Comment 1•10 years ago
|
||
Thanks for the report, we're looking at some changes that will make this better.
cc'ing Yvan and Stephen - this is exactly the sort of complaint we get about devtools and CORS debugging.
Updated•7 years ago
|
Product: Firefox → DevTools
Comment 2•7 years ago
|
||
I think the message are way better now. I can't point to a specific patch so I'm duping this on Bug 1475391 where we add an helpful link to MDN next to the CORS warning message
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•