886235 - XMLHttpRequest gets stuck on redirects for CORS requests in Web Workers

Status: RESOLVED DUPLICATE of bug 882458

(Core :: DOM: Workers, defect)

Description

[Victor Costan]

Attachment: index.html

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.52 Safari/537.36

Steps to reproduce:

I am firing a CORS XMLHttpRequest in a Web Worker.


Actual results:

The server responds with a 302, which is not followed


Expected results:

Firing the same request outside the Web Worker results in the 302 being followed. I expect the same behavior to happen inside the Web Worker.

The attached test case illustrates the issue, and passes in Google Chrome.

Comment 1

[Victor Costan]

I also uploaded the test case to jsbin, for easy inspection.
http://jsbin.com/ekixoq/1

FWIW, I also tried this on the builds from the Beta and Aurora channels.

Comment 2

[:xKhorasan]

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Firefox/31.0
Build ID: 20140420030202

test case for comment 0 and comment 1 not works, but I could confirm this bug if I add xhr.onerror handler to catch error.
http://jsbin.com/ekixoq/4

Comment 3

[:xKhorasan]

Attachment: rebased attachment 761764 to current mozilla-central

Hmm, it seems that bug 882458 treats similar issue, and when apply the patch (attachment 761764 [details] [diff] [review]) to current mozilla-central [1] source tree and build, I can confirm that reported test case in comment 1 and comment 4 both show "Test result: PASSED".

[1] http://hg.mozilla.org/mozilla-central/rev/180254

Maybe the root cause of this bug is same to bug 882458, so we can resolve this bugs as DUPLICATE of bug 882458?

Comment 4

[Ben Turner (not reading bugmail, use the needinfo flag!)]

Yeah, let's DUP.