is_well_formed_original_string()

bool xtd::uri::is_well_formed_original_string

(

)

Indicates whether the string used to construct this xtd::uri was well-formed and is not required to be further escaped.

Returns

bool A bool value that is true if the string was well-formed; else false.

Remarks

The string is considered to be well-formed in accordance with RFC 2396 and RFC 2732 by default. If International Resource Identifiers (IRIs) or Internationalized Domain Name (IDN) parsing is enabled, the string is considered to be well-formed in accordance with RFC 3986 and RFC 3987

The string is considered poorly formed, causing the method to return false, if any of the following conditions occur.

Error	Example
The string is not correctly escaped.	http://www.contoso.com/path???/file name
The string is an absolute xtd::uri that represents an implicit file xtd::uri.	c:\directory\filename
The string is an absolute URI that is missing a slash before the path.	file://c:/directory/filename
The string contains unescaped backslashes even if they are treated as forward slashes.	http:\host/path/file
The string represents a hierarchical absolute xtd::uri and does not contain "://".	www.contoso.com/path/file
The parser for the xtd::uri.scheme indicates that the original string was not well-formed.	The example depends on the scheme of the URI.

By default, the string used to construct this xtd::uri are considered well-formed in accordance with RFC 2396 and RFC 2732.

When International Resource Identifier (URI) and Internationalized Domain Name (IDN) support are enabled, the string used to construct this xtd::uri are considered well-formed in accordance with RFC 3986 and RFC 3987. Punycode names used to support URI contain only ASCII characters and always start with the xn– prefix.

For more information on URI support, see the Remarks section for the xtd::uri class.