929160 - failed cross-domain XHR requests don't log to the console

Status: RESOLVED WORKSFORME

(DevTools :: Console, defect, P3)

Description

[Davor Spasovski [:spasovski]]

It would be nice to have something like Chrome's console output: http://cl.ly/image/1f3X040f2e2C

Right now you can manually inspect the request in the network tab, see the 500, analyze the headers and determine no CORS enabled but we could be more developer-friendly since response headers aren't the easiest thing to read.

Comment 1

[Mihai Sucan [:msucan]]

This seems to be related to the work the security engineering team is doing. This needs platform work to report the errors. Mark, is this being worked on? Should we move this bug to a different component?

Comment 2

[Thomas Wisniewski]

These days, the Firefox web console logs a similar warning, so this bug might as well be closed:

>Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at <URL> (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).