Open Bug 1601290 Opened 6 years ago Updated 5 years ago

Upgrade Insecure Requests impacts Response objects weirdly

Categories

(Core :: DOM: Security, defect, P3)

Product:
Core
Component:
DOM: Security
Type:
defect

Tracking

()

People

(Reporter: annevk, Unassigned)

Details

(Whiteboard: [domsecurity-backlog2])

  1. Navigate to https://www.w3.org/ (and verify they still use this Upgrade Insecure Requests).
  2. fetch("http://www.w3.org/").then(console.log)
  3. fetch("https://www.w3.org/").then(console.log)

Redirected should not be true for either. Response type should be the same (though see https://github.com/w3c/webappsec-upgrade-insecure-requests/issues/20 for that one). I wanted to write tests for this, but see https://github.com/w3c/webappsec-upgrade-insecure-requests/issues/19.

Priority: -- → P3
Whiteboard: [domsecurity-backlog2]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.