Comments on: URL parsing and manipulation in .NET

By: Damien Guard

Damien Guard — Sun, 11 Apr 2010 05:21:06 +0000

It’s a good solution for general parsing operations even in a server environment where you want to do things like manipulate page parameters etc. (which is what it was originally designed for)

Any regex based parsing will be less well performing than a hand-coded parser – this applies to any parsing not just this one or url parsing.

[)amien

By: Michael

Michael — Sun, 11 Apr 2010 05:08:52 +0000

I’ve been collecting versions of different solutions that parse URLS and unfortunately, this one is by far the worst performing solution. Uri for all its weaknesses can process a million encode/decodes in about .4 seconds in my test environment. The second best solution which breaks more out than yours here is about 3 times slower than that but its versatile but I’m looking for something better performing still. But the regex solution above takes about a minute to process a million encode/decodes. That tracks to about 142 times slower. Sorry. Regex is a poor solution for parsing on the serverside.

By: guitarpoet

guitarpoet — Mon, 18 May 2009 06:55:54 +0000

Hello, I think the code has a bug and I had rewrite it like this:
private const string urlDecodeRegex = @”([^:]+)://(([^:@]+)(:([^@]+))?@)?([^:/?#]+)(:([\d]+))?([^?#]+)?(\?([^#]+))?(#(.*))?”;

By: Ziv Rozzbach

Ziv Rozzbach — Sun, 05 Oct 2008 15:00:33 +0000

Nice, but it does not do one thing: splitting the host from the domain
so if I enter reag123.afsda123.ukdomain.co.uk it will return me: ukdomain.co.uk

Anyone have any idea how can I do it ?

By: MrToes

MrToes — Mon, 12 May 2008 16:09:24 +0000

It’s also remarkably intolerant of syntax problems. There’s also a problem with the Uri class (in .NET 2.0 Compact Framework at least) where creating it with a string that has leading spaces causes memory corruption. Lovely. We have our own Uri class to fix this (and other) problems. Backward slashes resulting in FormatExceptions is another one that comes to mind. Quite possibly all this is fixed in new shiny .NET versions.

So, how long is it till V-day? :)

By: Damien Guard

Damien Guard — Sat, 03 May 2008 10:34:48 +0000

Thanks for spotting and figuring that out Ross – I must have broken it during the reformatting exercise when I switched to this theme.

[)amien

By: Russ

Russ — Fri, 02 May 2008 17:02:32 +0000

I found the problem, it’s in the regular expression.. Here’s the new line.

private const string urlDecodeRegex = @”([^:]+)://(([^:@]+)(:([^@]+))?@)?([^:/?#]+)(:([d]+))?([^?#]+)?(\?([^#]+))?(#(.*))?”;

By: Russ

Russ — Fri, 02 May 2008 16:52:15 +0000

This works well, but any attempts that I make to use an imported query string dont seem to work. I can build a querystring and export ok, but importing one fails.

Is there a download of this as a .cs class file?

By: Damien Guard

Damien Guard — Fri, 11 Apr 2008 09:56:33 +0000

@Mike: Well you could but if that’s all you want you may as well just grab the string up to the final / with urlString.Substring(0,urlString.LastIndexOf(‘/’)-1)

[)amien

By: Mike

Mike — Tue, 18 Mar 2008 02:46:36 +0000

If I had this: http://damieng.com/blog/2006/07/07/URL_parsing_and_manipulation_in_NET

How could I get just this part?
http://damieng.com/blog/2006/07/07