Open
Bug 1445635
Opened 7 years ago
Updated 2 years ago
Display a message when a resource fetch has been rejected because of CORS
Categories
(Core :: Networking: HTTP, enhancement, P5)
Core
Networking: HTTP
Tracking
()
NEW
People
(Reporter: julienw, Unassigned)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
9.02 KB,
image/png
|
Details |
When some resource fetch fails because of CORS, we have an error on the JS side that is "NetworkError when attempting to fetch resource." and nothing more to help debugging.
Chrome displays a nice error in the console (see attachment), we should have something similar.
Comment 1•7 years ago
|
||
Christoph, do you have an idea how to update the message to be more clear that it failed because of CORS?
Flags: needinfo?(ckerschb)
Comment 2•7 years ago
|
||
It would also be helpful to provide a stack trace for the code which initiated the fetch, where possible/applicable.
Updated•7 years ago
|
Component: Developer Tools: Console → Networking: HTTP
Product: Firefox → Core
Comment 3•7 years ago
|
||
(In reply to Brian Grinstead [:bgrins] from comment #1)
> Christoph, do you have an idea how to update the message to be more clear
> that it failed because of CORS?
In fact, vino is working on it, see:
https://bugzilla.mozilla.org/show_bug.cgi?id=1442551#c5
Should land within this cycle.
Flags: needinfo?(ckerschb)
Reporter | ||
Comment 4•7 years ago
|
||
> Christoph, do you have an idea how to update the message to be more clear that it failed because of CORS?
Just to be clear, the NetworkError we get is at the "fetch" call site. That it's shown in the console depends on the code. I think it would be a good idea to unconditionally show an error in the console like Chrome does.
Updated•7 years ago
|
Priority: -- → P5
Whiteboard: [necko-triaged]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•