All issues

Search results

Normative references to discontinued specs in Upgrade Insecure Requests

Status: Open.

#34 In w3c/webappsec-upgrade-insecure-requests;

· dontcallmedom-bot opened on Aug 30, 2024

Broken references in Upgrade Insecure Requests

Status: Open.

#33 In w3c/webappsec-upgrade-insecure-requests;

· dontcallmedom-bot opened on Feb 1, 2023

Update usage of "responsible document" and "responsible browsing context".

Status: Open.

#27 In w3c/webappsec-upgrade-insecure-requests;

· miketaylr opened on Mar 15, 2022

Response type

Status: Open.

#20 In w3c/webappsec-upgrade-insecure-requests;

· annevk opened on Dec 4, 2019

Testing

Status: Open.

#19 In w3c/webappsec-upgrade-insecure-requests;

· annevk opened on Dec 4, 2019

Use of "incumbent settings object" in "Policy inheritance" section does not make sense

Status: Open.

#17 In w3c/webappsec-upgrade-insecure-requests;

· bzbarsky opened on Jun 3, 2019

Explicitly mention if downloads should be upgraded to HTTPS or not

Status: Open.

#16 In w3c/webappsec-upgrade-insecure-requests;

· ckerschb opened on Mar 14, 2019

protected resource’s URL

Status: Open.

#15 In w3c/webappsec-upgrade-insecure-requests;

· hiroshige-g opened on Feb 11, 2019

Should loopback and other trusted urls be upgraded?

Status: Open.

#14 In w3c/webappsec-upgrade-insecure-requests;

· jonathanKingston opened on May 10, 2018

Upstream relevant bits and pieces to HTML.

Status: Open.

#5 In w3c/webappsec-upgrade-insecure-requests;

· mikewest opened on May 11, 2016

Need a way to detect upgrading

Status: Open.

#3 In w3c/webappsec-upgrade-insecure-requests;

· takenspc opened on Mar 25, 2016

Use of the Vary: Header.

Status: Open.

#2 In w3c/webappsec-upgrade-insecure-requests;

· ylafon opened on Jan 15, 2016