w3c webappsec-change-password-url issues

w3c / webappsec-change-password-url

A Well-Known URL for Changing Passwords

https://w3c.github.io/webappsec-change-password-url/

Other

899 stars 27 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Drop a reference to Request's synchronous flag, which was removed from the Fetch spec.

#47 hober closed 3 months ago
0
Normative references to discontinued specs in A Well-Known URL for Changing Passwords

#42 dontcallmedom-bot opened 9 months ago
0
Add Backdrop CMS as a tool which implements this standard

#40 danieljrmay closed 2 years ago
1
Be explicit that this specification is about "changing a password", not "resetting a password"

#39 danieljrmay opened 2 years ago
0
Update README.md

#38 vasilii-sv closed 2 years ago
2
Add 1Password

#37 oliverdunk closed 2 years ago
2
Any follow-up drafts for fully automated password change?

#34 dumblob opened 3 years ago
6
Add Elaine Knight as an editor of the HTTP response code reliability document.

#33 hober closed 3 years ago
0
Register with IANA

#32 hober opened 3 years ago
0
Update references & redirects to these documents

#31 hober opened 3 years ago
0
Migrate from WICG

#30 wseltzer closed 4 years ago
0
Specifying navigations affected by .well-known/change-password

#29 battre opened 4 years ago
0
https://archive.org/download/iptvsmarterstvbox-2.2.2.1/yelbastv.m3u

#28 musty1974 closed 4 years ago
0
Broken reference for "Appropriate Use of Well-Known URIs"

#26 psimonyi opened 4 years ago
0
response-code-reliability checking for OK Status

#24 battre opened 4 years ago
0
Main branch should be named 'main'

#23 hober closed 4 years ago
1
Use GitHub Actions for deploying spec to the gh-pages branch

#22 hober closed 4 years ago
0
What about a link relation type?

#21 dret opened 4 years ago
3
Malicious subdomain concern

#20 hober opened 4 years ago
3
Expand security considerations section

#19 hober opened 4 years ago
1
Migrate to WebAppSec?

#18 hober closed 3 years ago
7
Update WELLKNOWN RFC to RFC8615

#17 gvangool closed 4 years ago
1
Who supports this?

#16 marcoscaceres opened 4 years ago
9
Clarify that redirects should be followed to resolve the Change Password URL

#15 rmondello opened 4 years ago
1
Consider ways of differentiating implementation and poor error pages

#14 oliverdunk closed 4 years ago
6
Restrict redirection status codes to temporary ones

#13 tregagnon closed 4 years ago
2
Pathway to W3C adoption

#12 nicksantamaria closed 5 years ago
3
Adopt pr-preview

#11 hober closed 5 years ago
1
Add a parameter to specify a language version of the app

#10 davidkmenta closed 5 years ago
1
Clarify interpretation of RFC5785 §1.1

#9 hober opened 5 years ago
0
Consider restricting the target of the redirect to be same-origin

#8 hober closed 4 years ago
3
What should clients do on OK status?

#7 jgimenez opened 5 years ago
1
base origin has multiple apps

#6 jbtule closed 5 years ago
6
Use RFC2119 to put constraints on actors doing $foo, not on things being $bar or having $baz

#5 frivoal closed 5 years ago
2
Add informative text clarifying that servers may use complex logic to determine where to redirect to

#4 craigfrancis opened 5 years ago
4
Punycode?

#3 mikewest closed 4 years ago
3
Consider adding a bit more detail to the generation algorithm.

#2 mikewest closed 5 years ago
3
Figure out how to get this to show up on wicg.github.io

#1 hober closed 5 years ago
1