A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://learn.microsoft.com/en-us/dotnet/api/system.uri.iswellformedoriginalstring below:

Uri.IsWellFormedOriginalString Method (System) | Microsoft Learn

Uri.IsWellFormedOriginalString Method Definition

Indicates whether the string used to construct this Uri was well-formed and does not require further escaping.

public:
 bool IsWellFormedOriginalString();
public bool IsWellFormedOriginalString();
member this.IsWellFormedOriginalString : unit -> bool
Public Function IsWellFormedOriginalString () As Boolean
Returns

true if the string was well-formed; otherwise, 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 Uri that represents an implicit file 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 Uri and does not contain "://". www.contoso.com/path/file The parser for the 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 Uri are considered well-formed in accordance with RFC 2396 and RFC 2732.

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

For more information on IRI support, see the Remarks section for the Uri class.

See also

Collaborate with us on GitHub

The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide. In this article

Was this page helpful?


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4