Closed Bug 1455332 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 9039 - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=180347

Categories

(Testing :: web-platform-tests, enhancement, P4)

enhancement

Tracking

(firefox61 fixed)

RESOLVED FIXED
mozilla61
Tracking Status
firefox61 --- fixed

People

(Reporter: wptsync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream][stockwell infra])

Sync web-platform-tests PR 9039 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/w3c/web-platform-tests/pull/9039
Details from upstream follow.

Youenn Fablet <youennf@gmail.com> wrote:
>  WebKit export of https://bugs.webkit.org/show_bug.cgi?id=180347
>  
>  fetch()'s redirect feature is insecure combined with "no-cors" or "cors"
>  
>  
>
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Ran 3 tests and 116 subtests
OK     : 3
PASS   : 80
FAIL   : 36

New tests that have failures or other problems:
/fetch/api/redirect/redirect-mode-worker.html
    Redirect 301 in follow redirect and cors mode: FAIL
    Redirect 301 in follow redirect and no-cors mode: FAIL
    Redirect 301 in manual redirect and no-cors mode: FAIL
    Redirect 302 in follow redirect and cors mode: FAIL
    Redirect 302 in follow redirect and no-cors mode: FAIL
    Redirect 302 in manual redirect and no-cors mode: FAIL
    Redirect 303 in follow redirect and cors mode: FAIL
    Redirect 303 in follow redirect and no-cors mode: FAIL
    Redirect 303 in manual redirect and no-cors mode: FAIL
    Redirect 307 in follow redirect and cors mode: FAIL
    Redirect 307 in follow redirect and no-cors mode: FAIL
    Redirect 307 in manual redirect and no-cors mode: FAIL
    Redirect 308 in follow redirect and cors mode: FAIL
    Redirect 308 in follow redirect and no-cors mode: FAIL
    Redirect 308 in manual redirect and no-cors mode: FAIL
/fetch/api/redirect/redirect-mode.html
    Redirect 301 in follow redirect and cors mode: FAIL
    Redirect 301 in follow redirect and no-cors mode: FAIL
    Redirect 301 in manual redirect and no-cors mode: FAIL
    Redirect 302 in follow redirect and cors mode: FAIL
    Redirect 302 in follow redirect and no-cors mode: FAIL
    Redirect 302 in manual redirect and no-cors mode: FAIL
    Redirect 303 in follow redirect and cors mode: FAIL
    Redirect 303 in follow redirect and no-cors mode: FAIL
    Redirect 303 in manual redirect and no-cors mode: FAIL
    Redirect 307 in follow redirect and cors mode: FAIL
    Redirect 307 in follow redirect and no-cors mode: FAIL
    Redirect 307 in manual redirect and no-cors mode: FAIL
    Redirect 308 in follow redirect and cors mode: FAIL
    Redirect 308 in follow redirect and no-cors mode: FAIL
    Redirect 308 in manual redirect and no-cors mode: FAIL
/service-workers/service-worker/fetch-event-redirect.https.html
    Non-navigation, manual redirect, no-cors mode Request redirected to cors with credentials should fail: FAIL
    Non-navigation, manual redirect, no-cors mode Request redirected to cors without credentials should fail: FAIL
    Non-navigation, manual redirect, no-cors mode Request redirected to no-cors with credentials should fail: FAIL
    Non-navigation, manual redirect, no-cors mode Request redirected to no-cors without credentials should fail: FAIL
    Non-navigation, manual redirect, no-cors mode Request redirected to same-origin with credentials should fail: FAIL
    Non-navigation, manual redirect, no-cors mode Request redirected to same-origin without credentials should fail: FAIL
These failures are largely due to bugs in the test.  I have an upstream PR to fix them here:

https://github.com/w3c/web-platform-tests/pull/10536
Whiteboard: [wptsync downstream error] → [wptsync downstream]
https://hg.mozilla.org/mozilla-central/rev/7dc3d642ef5b
https://hg.mozilla.org/mozilla-central/rev/bfa2755e73af
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Whiteboard: [wptsync downstream] → [wptsync downstream][stockwell infra]
You need to log in before you can comment on or make changes to this bug.