Issues · w3c/webappsec-upgrade-insecure-requests · GitHub
Skip to content

Issues: w3c/webappsec-upgrade-insecure-requests

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

12 Open 9 Closed
12 Open 9 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Normative references to discontinued specs in Upgrade Insecure Requests
#34 opened Aug 30, 2024 by dontcallmedom-bot
1 task
Broken references in Upgrade Insecure Requests
#33 opened Feb 1, 2023 by dontcallmedom-bot
3 tasks
Update usage of "responsible document" and "responsible browsing context".
#27 opened Mar 15, 2022 by miketaylr
Response type
#20 opened Dec 4, 2019 by annevk
Testing
#19 opened Dec 4, 2019 by annevk
1
Use of "incumbent settings object" in "Policy inheritance" section does not make sense
#17 opened Jun 3, 2019 by bzbarsky
1
Explicitly mention if downloads should be upgraded to HTTPS or not
#16 opened Mar 14, 2019 by ckerschb
2
protected resource’s URL
#15 opened Feb 11, 2019 by hiroshige-g
1
Should loopback and other trusted urls be upgraded?
#14 opened May 10, 2018 by jonathanKingston
7
Upstream relevant bits and pieces to HTML.
#5 opened May 11, 2016 by mikewest
1
Need a way to detect upgrading
#3 opened Mar 25, 2016 by takenspc
Use of the Vary: Header.
#2 opened Jan 15, 2016 by ylafon
ProTip! Updated in the last three days: updated:>2024-11-20.