Closed Bug 1136838 Opened 9 years ago Closed 8 years ago

Cors is not working on 36.0

Categories

(Core :: DOM: Security, defect)

36 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: phelipemaia, Unassigned)

References

Details

(Whiteboard: [domsecurity-backlog])

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36

Steps to reproduce:

Make a CORS request


Actual results:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at "URL". This can be fixed by moving the resource to the same domain or enabling CORS.


Expected results:

Make the request as old versions
Please provide a testcase with steps to reproduce
Flags: needinfo?(phelipemaia)
Hi Matthias,

Please go to qa.exceedlabs.com and try to login using an email and password. You will see the error on console.
Flags: needinfo?(phelipemaia)
Asana also has this issue while trying to upload attachments using CORS
Asana also has this issue while trying to upload attachments using CORS
Seems related to https://bugzilla.mozilla.org/show_bug.cgi?id=1137432.

For both pmia and phips, the cross-domain requests are being made against hosts with underscores.

Have a repro that I can make available, where a cross domain requests work to S3 buckets without underscores, but fail on buckets with underscores.
Component: Untriaged → Security
OS: Windows 8.1 → All
Product: Firefox → Core
Hardware: x86_64 → All
See Also: → 1137432
This is probably being caused by bug 1136616.
Depends on: 1136616
Making my way through old bugs here. Is this working again after Bug 1136616 landed? Otherwise I'll find someone to take a look at this problem.
Component: Security → DOM: Security
Flags: needinfo?(phelipemaia)
Whiteboard: [domsecurity-backlog]
Closing this bug as INCOMPLETE - potentially it's not an issue anymore.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(phelipemaia)
You need to log in before you can comment on or make changes to this bug.