From bb1948affe8ebb383d1fc905fb824ede4340fabd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Anders=20=C3=85berg?= Date: Wed, 21 Feb 2024 21:25:05 +0100 Subject: [PATCH] Update index.bs --- index.bs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.bs b/index.bs index e66824fec..82887af5f 100644 --- a/index.bs +++ b/index.bs @@ -1344,7 +1344,7 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S - The [=determines the set of origins on which the public key credential may be exercised|origin=]'s [=scheme=] must be `https`. - The [=determines the set of origins on which the public key credential may be exercised|origin=]'s [=port=] is unrestricted. - For example, given a [=[RP]=] whose origin is `https://login.example.com:1337`, then the following [=RP ID=]s are valid: `login.example.com` (default) and `example.com`, but not `m.login.example.com` and not `com`. Another example of a valid origin is `http://localhost:8000`, due to the origin being `localhost` + For example, given a [=[RP]=] whose origin is `https://login.example.com:1337`, then the following [=RP ID=]s are valid: `login.example.com` (default) and `example.com`, but not `m.login.example.com` and not `com`. Another example of a valid origin is `http://localhost:8000`, due to the origin being `localhost`. This is done in order to match the behavior of pervasively deployed ambient credentials (e.g., cookies, [[RFC6265]]). Please note that this is a greater relaxation of "same-origin" restrictions than what