True if url is a valid absolute URI suitable for a URL-mode elicitation.
Per client/elicitation §"URL Mode Elicitation Requests" (2025-11-25) the
url parameter MUST contain a valid URL, and its schema marks the field
format: uri. URL-mode elicitation drives browser navigation, so the scheme
is additionally restricted (case-insensitively) to http or https: a
non-web scheme such as file://, ftp:// or ws:// is rejected even when
it carries a //authority. (The spec only SHOULDs HTTPS, so plain http is
accepted rather than rejected here.) Beyond the scheme this requires an
absolute URI: the scheme is followed by : and a hierarchical //authority
with a non-empty host. Relative references, bare strings such as
"not a url", and scheme:-only values are rejected. Validation is
permissive about the path/query/fragment so any real https://… consent or
OAuth URL passes.
True if url is a valid absolute URI suitable for a URL-mode elicitation.
Per client/elicitation §"URL Mode Elicitation Requests" (2025-11-25) the url parameter MUST contain a valid URL, and its schema marks the field format: uri. URL-mode elicitation drives browser navigation, so the scheme is additionally restricted (case-insensitively) to http or https: a non-web scheme such as file://, ftp:// or ws:// is rejected even when it carries a //authority. (The spec only SHOULDs HTTPS, so plain http is accepted rather than rejected here.) Beyond the scheme this requires an absolute URI: the scheme is followed by : and a hierarchical //authority with a non-empty host. Relative references, bare strings such as "not a url", and scheme:-only values are rejected. Validation is permissive about the path/query/fragment so any real https://… consent or OAuth URL passes.