Closed
Bug 696849
Opened 13 years ago
Closed 13 years ago
add test cases observing cross-domain XHR in chrome code
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: julian.reschke, Assigned: julian.reschke)
References
Details
Attachments
(1 file)
6.72 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
Extend test_XHR_redirects.js so that the cross-domain case is tested as well.
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #569336 -
Flags: review?(bzbarsky)
Comment 2•13 years ago
|
||
Comment on attachment 569336 [details] [diff] [review] modified tests to also test cross-domain So what's changing to make these not same-origin is the port? r=me
Attachment #569336 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 3•13 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #2) > Comment on attachment 569336 [details] [diff] [review] [diff] [details] [review] > modified tests to also test cross-domain > > So what's changing to make these not same-origin is the port? Yep, that's my understanding of the same-origin policy.
Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Updated•13 years ago
|
Assignee: nobody → julian.reschke
Comment 4•13 years ago
|
||
In my queue, which is going via try then onto inbound: https://tbpl.mozilla.org/?tree=Try&rev=d3d2522ed095 Thanks :-)
Comment 5•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a0b6d0a04e4a
Target Milestone: --- → mozilla10
Comment 6•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a0b6d0a04e4a
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•