PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Valid URL not accepted in Website URL field

  1. I have a form that includes a Website URL field. When I enter the following URL into that field, it will not accept it and comes back with the message:

    Please enter a valid Website URL (i.e. http://www.gravityforms.com)

    The URL in question is:

    http://searchstorage.techtarget.com/tip/0,289483,sid5_gci1515806,00.html?track=NL-52&ad=774956HOUSE&asrc=EM_NLN_11964053&uid=6058125

    The URL is indeed valid, albeit a tad strange. What is it about that URL that is causing the Website URL field heartburn?

    Thanks,

    John

    Posted 14 years ago on Monday November 1, 2010 | Permalink
  2. We will look into why this URL is being rejected. The Website URL uses a regular expression to check the format, and something in this extremely long URL is triggering the regular expression validation. The field was intended for simple URLS (ex. techtarget.com) so the regular expression isn't expecting extremely long urls with complex querystrings.

    Posted 14 years ago on Monday November 1, 2010 | Permalink
  3. Thanks for the reply, Carl. I figured it was something like that. I know I'm pushing the boundaries with this one. :-) If worse comes to worst, I suppose I can use a plain text field to work around the issue, but it would be nice to have the validation already done.

    Posted 14 years ago on Monday November 1, 2010 | Permalink
  4. kfawcett
    Member

    I'm actually running into the same problem. I was testing my form and the URL I tested had an @ in it and it failed to validate. I've also seen a few other forms fail with these symbols ( ) so far.

    Posted 13 years ago on Thursday December 2, 2010 | Permalink
  5. The website URL field was designed for simple urls (ex. http://www.yahoo.com), not complex querystring containing URLS. The regular expression checks to make sure the URL is in the correct format. If we have to take into account complex query string URL's then it's going to be less likely to catch that the URL is in the right format if they can use a large number of strange characters. If you require complex URL's with query string formatting you will probably need to use a standard input field rather than the web site field.

    Posted 13 years ago on Thursday December 2, 2010 | Permalink