You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Deal with TLS client certificates and HTTP authentication #2
I think referencing the Fetch concept is probably good. And then hopefully at some point someone makes that more precise (or maybe you end up killing it first).
Activity
Stub for #2.
Foxyroxy1 commentedon Feb 10, 2017
mikewest commentedon Mar 23, 2017
I landed a hand-wavey thing a while ago. I guess it should really be talking about https://fetch.spec.whatwg.org/#authentication-entry, but it's not clear to me how those exist/are stored/etc.
Thoughts?
mikewest commentedon Mar 23, 2017
(Step 6 of https://w3c.github.io/webappsec-clear-site-data/#clear-cookies)
annevk commentedon Mar 23, 2017
I'm not sure how they are stored either or what the requirements around that are. It seems implementations are allowed to pursue various strategies.
mikewest commentedon Mar 23, 2017
Ok. I'll wave my hands a little bit more in the hopes of clarity.
annevk commentedon Mar 23, 2017
I think referencing the Fetch concept is probably good. And then hopefully at some point someone makes that more precise (or maybe you end up killing it first).
Use Fetch terminology for HTTP authentication.