Merge pull request #3498 from hasheddan/md-links-oauth

(docs) Fix rendering of markdown links in OAuth docs HTML
This commit is contained in:
Wang Yan 2022-04-23 00:33:20 +08:00 committed by GitHub
commit 9332c3cc7b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -61,7 +61,7 @@ Content-Type: application/x-www-form-urlencoded
to be registered with the authorization server but should be set to a to be registered with the authorization server but should be set to a
meaningful value in order to allow auditing keys created by unregistered meaningful value in order to allow auditing keys created by unregistered
clients. Accepted syntax is defined in clients. Accepted syntax is defined in
[RFC6749 Appendix A.1](https://tools.ietf.org/html/rfc6749#appendix-A.1) <a href="https://tools.ietf.org/html/rfc6749#appendix-A.1" rel="noopener noreferrer nofollow" target="_blank">RFC6749 Appendix A.1</a>.
</dd> </dd>
<dt> <dt>
<code>access_type</code> <code>access_type</code>
@ -126,7 +126,7 @@ Content-Type: application/x-www-form-urlencoded
<dd> <dd>
(REQUIRED) The scope granted inside the access token. This may be the (REQUIRED) The scope granted inside the access token. This may be the
same scope as requested or a subset. This requirement is stronger than same scope as requested or a subset. This requirement is stronger than
specified in [RFC6749 Section 4.2.2](https://tools.ietf.org/html/rfc6749#section-4.2.2) specified in <a href="https://tools.ietf.org/html/rfc6749#section-4.2.2" rel="noopener noreferrer nofollow" target="_blank">RFC6749 Section 4.2.2</a>
by strictly requiring the scope in the return value. by strictly requiring the scope in the return value.
</dd> </dd>
<dt> <dt>
@ -142,7 +142,7 @@ Content-Type: application/x-www-form-urlencoded
<code>issued_at</code> <code>issued_at</code>
</dt> </dt>
<dd> <dd>
(Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt" rel="noopener noreferrer nofollow" target="_blank">RFC3339</a>-serialized UTC
standard time at which a given token was issued. If <code>issued_at</code> is omitted, the standard time at which a given token was issued. If <code>issued_at</code> is omitted, the
expiration is from when the token exchange completed. expiration is from when the token exchange completed.
</dd> </dd>