Set this property to true if the URIs with this custom
scheme will have an authority component (a host for custom schemes).
Specifically, if you have a URI of the following form you should set the
HasAuthorityComponent value as listed.
When this property is set to true, the URIs with this scheme will be
interpreted as having a
scheme and host
origin similar to an http URI. Note that the port and user
information are never included in the computation of origins for
custom schemes.
If this property is set to false, URIs with this scheme will have an
opaque origin
similar to a data URI.
This property is false by default.
Note: For custom schemes registered as having authority component,
navigations to URIs without authority of such custom schemes will fail.
However, if the content inside WebView2 references
a subresource with a URI that does not have
an authority component, but of a custom scheme that is registered as
having authority component, the URI will be interpreted as a relative path
as specified in RFC3986.
For example, custom-scheme-with-authority:path will be interpreted
as custom-scheme-with-authority://host/path.
However, this behavior cannot be guaranteed to remain in future
releases so it is recommended not to rely on this behavior.
Set this property to true if the URIs with this custom scheme will have an authority component (a host for custom schemes). Specifically, if you have a URI of the following form you should set the HasAuthorityComponent value as listed.
| URI | Recommended HasAuthorityComponent value | | -- | -- | | custom-scheme-with-authority://host/path | true | | custom-scheme-without-authority:path | false |
When this property is set to true, the URIs with this scheme will be interpreted as having a scheme and host
origin similar to an http URI. Note that the port and user information are never included in the computation of origins for custom schemes. If this property is set to false, URIs with this scheme will have an opaque origin
similar to a data URI. This property is false by default.
Note: For custom schemes registered as having authority component, navigations to URIs without authority of such custom schemes will fail. However, if the content inside WebView2 references a subresource with a URI that does not have an authority component, but of a custom scheme that is registered as having authority component, the URI will be interpreted as a relative path as specified in RFC3986. For example, custom-scheme-with-authority:path will be interpreted as custom-scheme-with-authority://host/path. However, this behavior cannot be guaranteed to remain in future releases so it is recommended not to rely on this behavior.