![[Be el o ge]](http://blog.project-sierra.de/wp-content/themes/cutline-3-column-split-11/images/header_2.jpg "[Be el o ge]")
A few days ago I had to analyze a string, figure out whether it is a URI and if yes, then do something with parts of the URI, like the host, the pathname and the parameters. Since I was coding in C# I thought the Uri class would be just ideal for that.
So first I implemented this
Uri myUri; try { myUri = new Uri(myUrlString); } catch (UriFormatException) { // do something }
Then however I realized that there is a function for testing the validity of a string:
Uri myUri; if (Uri.IsWellFormedUriString(myUrlString)) { myUri = new Uri(myUrlString); }
This is much nicer. I don’t like using exceptions to handle expected workflows. In this case the string can be a valid or invalid Uri, so really the if-then-else construction is nicer than the try-catch. The problem is that even though IsWellFormedUriString returns true you might not be able to create an Uri instance from it. Consider this small programm:
using System; namespace DemoConsoleApp { class MainClass { public static void Main(string[] args) { Uri myUri; string myUrl1 = "www.mydomain.de/test/file.aspx"; string myUrl2 = "http://www.mydomain.de/test/file.aspx"; Console.WriteLine(Uri.IsWellFormedUriString(myUrl1, UriKind.RelativeOrAbsolute)); Console.WriteLine(Uri.IsWellFormedUriString(myUrl2 ,UriKind.RelativeOrAbsolute)); try { myUri = new Uri(myUrl1); } catch (UriFormatException) { Console.WriteLine("Failed to create Uri from myUrl1"); } try { myUri = new Uri(myUrl2); } catch (UriFormatException) { Console.WriteLine("Failed to create Uri from myUrl2"); } } } }
The output is :
True True Failed to create Uri from myUrl1
According to the documentation, the first call of Uri.IsWellFormedUriString should returns false. If it did this would be also consistent with the constructor, which fails for myUrl1.
By default, the string is considered well-formed in accordance with RFC 2396 and RFC 2732. If International Resource Identifiers (IRIs) or Internationalized Domain Name (IDN) parsing is enabled, the string is considered 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
[...]
The string represents a hierarchical absolute Uri and does not contain “://” – www.contoso.com/path/file
