Comparison

mod_http_oauth2/README.markdown @ 5505:efe9e741f222

mod_http_oauth2: Correct loopback URL example The s in the scheme should not be there, only unencrypted http to loopback interface is allowed.
author Kim Alvefur <zash@zash.se>
date Thu, 01 Jun 2023 19:37:17 +0200
parent 5494:1bcf755c7bae
child 5506:37621c6e5c08
comparison
equal deleted inserted replaced
5504:7d9dce4e7dd0 5505:efe9e741f222
119 - If `application_type` equals `web` (or is not included) then all 119 - If `application_type` equals `web` (or is not included) then all
120 `redirect_uris` **MUST** be `https://` URIs and **MUST** use the 120 `redirect_uris` **MUST** be `https://` URIs and **MUST** use the
121 same hostname part as the `client_uri`. 121 same hostname part as the `client_uri`.
122 - If `application_type` equals `native` then all `redirect_uris` 122 - If `application_type` equals `native` then all `redirect_uris`
123 **MUST** match one of: 123 **MUST** match one of:
124 - Loopback `http://` URI, e.g. `https://127.0.0.1:8080/` 124 - Loopback HTTP URI, e.g. `http://127.0.0.1/` or `http://[::1]`
125 - Application-specific scheme, e.g. `com.example.app:/` 125 - Application-specific scheme, e.g. `com.example.app:/`
126 - The special OOB URI `urn:ietf:wg:oauth:2.0:oob` 126 - The special OOB URI `urn:ietf:wg:oauth:2.0:oob`
127 - Informative URIs such as policy and terms of service **MUST** use 127 - Informative URIs such as policy and terms of service **MUST** use
128 the same scheme (i.e. `https://`) and hostname as the `client_uri`. 128 the same scheme (i.e. `https://`) and hostname as the `client_uri`.
129 129