[wpt-sync] Sync PR 38113 - Mixed Content behavior related to CORS requests
Categories
(Core :: DOM: Security, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox111 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 38113 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/38113
Details from upstream follow.
moztomer <105853975+moztomer@users.noreply.github.com> wrote:
Mixed Content behavior related to CORS requests
Intro
This patch is about testing mixed content behavior regarding CORS requests. It should run successfully for all chromium based browsers that enabled mixed content upgrading and Firefox nightly.
Some background:
Since the implementation of Mixed content seems to differ from the spec according to its behavior with CORS requests. In the spec it says mixed content should NOT upgrade any CORS requests.
But the yet-implemented versions of mixed content auto upgrading do so. This patch is ensuring that mixed content auto upgrading is upgrading CORS requests, that is towards the spec is likely to be adjusted to.Test
- Creates a type an element (img, audio or video) with HTTP URL.
- Sets a crossOrigin attribute and a CORS header.
- Adds element from step 1 to document.
Expected result: URL of element gets successfully upgraded to HTTPS.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
| Assignee | ||
Comment 2•3 years ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 3 subtests
Status Summary
Firefox
OK : 1
PASS: 3
Chrome
OK : 1
PASS: 3
Safari
OK : 1
FAIL: 3
Links
Comment 4•3 years ago
|
||
| bugherder | ||
Description
•