Comments on: FastSharp - Rapid C# Scripting http://nicholasclarke.co.uk/blog/2008/02/17/fastsharp-rapid-c-scripting/ Thu, 28 Aug 2008 05:36:38 +0000 http://wordpress.org/?v=2.5.1 By: Nick Clarke http://nicholasclarke.co.uk/blog/2008/02/17/fastsharp-rapid-c-scripting/#comment-661 Nick Clarke Wed, 20 Feb 2008 21:01:55 +0000 http://nicholasclarke.co.uk/blog/2008/02/17/fastsharp-rapid-c-scripting/#comment-661 Hi Sebastien, You're right that the regex does not cover all of the valid URLs characters/patterns nor would it allow unicode characters etc. In my situation it works as I have control over the URL + its only used in a site with limited exposure so this simple approach works. If someone wanted to break up their URL this expression would not be the way to go, at least in its current state. I looked at the .Net docs and I could not find Uri.TryParse, there was a Uri.Parse but this is marked as obsolete. Is this in a special library or am I overlooking it? Cheers for your feedback Hi Sebastien,

You’re right that the regex does not cover all of the valid URLs characters/patterns nor would it allow unicode characters etc. In my situation it works as I have control over the URL + its only used in a site with limited exposure so this simple approach works.

If someone wanted to break up their URL this expression would not be the way to go, at least in its current state.

I looked at the .Net docs and I could not find Uri.TryParse, there was a Uri.Parse but this is marked as obsolete. Is this in a special library or am I overlooking it?

Cheers for your feedback

]]> By: Sebastien Lambla http://nicholasclarke.co.uk/blog/2008/02/17/fastsharp-rapid-c-scripting/#comment-659 Sebastien Lambla Wed, 20 Feb 2008 15:04:50 +0000 http://nicholasclarke.co.uk/blog/2008/02/17/fastsharp-rapid-c-scripting/#comment-659 The \w use is factually incorrect. As per the RFC on URIs, domain names (?[A-Za-z0-9]([A-Za-z0-9-]*[A-Za-z0-9]))?\.)*(?[A-Za-z]([A-Za-z-]*[A-Za-z])?) Your current regex would happily parse completely invalid urls formed of unicode characters. That said, this does not include any support for IRI and IDNs where more stop points are to be recognized... What's wrong with Uri.TryParse? :) The \w use is factually incorrect. As per the RFC on URIs, domain names
(?[A-Za-z0-9]([A-Za-z0-9-]*[A-Za-z0-9]))?\.)*(?[A-Za-z]([A-Za-z-]*[A-Za-z])?)

Your current regex would happily parse completely invalid urls formed of unicode characters.

That said, this does not include any support for IRI and IDNs where more stop points are to be recognized…

What’s wrong with Uri.TryParse? :)

]]>