Earlier today I needed URL input validation (my form prompted for a URL, I needed to validate that what was provided was a syntactically valid URL). URL validation is actually rather complicated, but the following regular expression worked for me:
This one allows both http and https, supports an optional port, and allows paths and query strings too. Oh, it also works with both JavaScript (and can thus be used with ) and CFML.

14 thoughts

  1. Great! I only just discovered the RegEx support in CF5 and above and this will come in very handy!
    Thanks Ben!

  2. How about using it in the comments text to change urls into actual <a> links that open in a new window?

  3. How to parse a URL:
    Captures end up being the scheme, authority, path, query and fragment.

  4. Mohamed, your Regex is excellent, but I’ve found a little hole in the thing: it matches even if you’re doubling the protocol, e.g.:
    The worse part is that, in CFMX7 when you try to cfhttp it, the Java engine throws the exception:
    500 HTTPClient Internal Error: unexpected exception ‘HTTPClient.ParseException: somesite.com.br is an invalid port number’ HTTPClient Internal Error: unexpected exception ‘HTTPClient.ParseException: somesite.com.br is an invalid port number’
    It’s a Java Exception, not even a CFMX exception. I’ll try to fix this down, but i’m not as skilled as you guys here are in regexes….

  5. Very good regex, I have been looking for this to replace the original Internet URL validation from the built-in that provided with .Net ver 2. This is very good replacement because it can suport port number

  6. The regular expression validates URL like the following:
    htp://www.mysite.com, or xyz://www.mysite.com
    The prefix protocol is wrong.
    In this way you can fix the problem:
    I have another question: it accept URL with double ‘.’. Can it possible having an URl with double ‘.’?

  7. Thank you very much!
    I’d been beating my head against the wall for the better part of a night trying to get a RegEx recipe for URLs from O’Reilly’s pocket reference to work in REFindNoCase (but it had pound signs and other chars to which CF objected). Wish I’d found your RegEx first! 🙂

Leave a Reply