Skip to content
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.

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

Clarify that credentials include HTTP auth #616

Merged
merged 3 commits into from Oct 14, 2017
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 6 additions & 8 deletions fetch.bs
Expand Up @@ -166,10 +166,9 @@ Standards.

<hr>

<p><dfn id=credentials export>Credentials</dfn> are HTTP cookies, TLS client certificates, and, for
HTTP authentication, <a lt="authentication entry">authentication entries</a> and <a
lt="proxy-authentication entry">proxy-authentication entries</a>. [[!COOKIES]] [[!TLS]]
[[!HTTP-AUTH]]
<p><dfn id=credentials export>Credentials</dfn> are HTTP cookies, TLS client certificates, and <a
lt="authentication entry">authentication entries</a> (for HTTP authentication). [[!COOKIES]]
[[!TLS]] [[!HTTP-AUTH]]

<hr>

Expand Down Expand Up @@ -1446,10 +1445,9 @@ is a <a>filtered response</a> whose

<h3 id=authentication-entries>Authentication entries</h3>

<p>An <dfn export>authentication entry</dfn> and a
<dfn export>proxy-authentication entry</dfn> are tuples of username, password, and realm,
associated with one or more <a for=/>requests</a>.

<p>An <dfn export>authentication entry</dfn> and a <dfn export>proxy-authentication entry</dfn> are
tuples of username, password, and realm, used for HTTP authentication, and associated with one or
more <a for=/>requests</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trailing dot went missing. Also, I'd make it "HTTP and HTTP proxy authentication" maybe?

<p>User agents should allow both to be cleared together with HTTP cookies and similar tracking
functionality.
<!-- fingerprinting -->
Expand Down