Skip to content

Expose nested browsing context status in RequestClient #41639

@jdm

Description

@jdm

We're missing step 2.2 of https://w3c.github.io/webappsec-upgrade-insecure-requests/#upgrade-request in our implementation in

// Step 2.2
// TODO If request’s client's target browsing context is a nested browsing context

This leads to timeouts in tests like https://github.com/servo/servo/blob/main/tests/wpt/tests/upgrade-insecure-requests/link-upgrade.sub.https.html because the iframes loaded from http URLs are never upgraded to https, so they get blocked as mixed content.

We need to:

You can test this against ./mach test-wpt tests/wpt/tests/upgrade-insecure-requests and ./mach test-wpt tests/wpt/tests/mixed-content; I would expect a bunch of new subtests going from TIMEOUT to a PASS/FAIL result.

Metadata

Metadata

Labels

A-content/scriptRelated to the script threadA-networkC-assignedThere is someone working on resolving the issueE-less-complexStraightforward. Recommended for a new contributor.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions