Closed
Bug 1090227
Opened 10 years ago
Closed 9 years ago
CORS only error message doesn't help debug issues
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1121824
People
(Reporter: rik, Unassigned, Mentored)
References
Details
(Whiteboard: [lang=c++])
When debugging bug 1087327 last week, Firefox was not helping me understand the issue. Any CORS error will be logged as: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. This can be fixed by moving the resource to the same domain or enabling CORS. In contrast, Chrome and Safari gave me a message that was more useful: XMLHttpRequest cannot load https://support.allizom.org/api/2/question/. Request header field Authorization is not allowed by Access-Control-Allow-Headers. We should improve our reporting to help web developers.
Updated•10 years ago
|
Mentor: bzbarsky
Whiteboard: [lang=c++]
Comment 1•10 years ago
|
||
Relevant code: LogBlockedRequest in nsCrossSiteListenerProxy.cpp and the CrossSiteRequestBlocked property in http://mxr.mozilla.org/mozilla-central/source/dom/locales/en-US/chrome/security/security.properties.
Comment 2•9 years ago
|
||
Is very annoying this problem! Maybe add an alert for the Open Web App for use the mozSystem in XHR request, and the systemXHR in the manifest.webapp will be very useful.
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•