Merge pull request #434 from thibmeu/main

Add RFC9110 reference when parsing header with multiple challenges
ietf-wg-privacypass · Aug 10, 2023 · 338dd2a · 338dd2a
2 parents f285124 + fbbdb6e
commit 338dd2a
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 1 deletion.
diff --git a/draft-ietf-privacypass-architecture.md b/draft-ietf-privacypass-architecture.md
diff --git a/draft-ietf-privacypass-auth-scheme.md b/draft-ietf-privacypass-auth-scheme.md
@@ -265,7 +265,7 @@ current connection is not authoritative (according to the TLS certificate).
 Caching and pre-fetching of tokens is discussed in {{caching}}.
 
 Note that it is possible for the WWW-Authenticate header field to include
-multiple challenges. This allows the origin to indicate support for different
+multiple challenges ({{!RFC9110, Section 11.6.1}}). This allows the origin to indicate support for different
 token types, issuers, or to include multiple redemption contexts. For example,
 the WWW-Authenticate header field could look like this: