Title: Accept URL that doesn’t start with http/https
Last modified: March 28, 2020

---

# Accept URL that doesn’t start with http/https

 *  Resolved [abazeed](https://wordpress.org/support/users/abazeed/)
 * (@abazeed)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/accept-url-that-doesnt-start-with-http-https/)
 * Hello team,
 * The Website field that should accept a valid URL raises an error if the URL doesn’t
   start with the scheme (http, https).
 * Can you please update your validation rules to accept such URLs?
    Like: facebook.
   com, [http://www.facebook.com](http://www.facebook.com)
 * Best Regards,

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [Laura – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support8/)
 * (@wpmudev-support8)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/accept-url-that-doesnt-start-with-http-https/#post-12606712)
 * Hello [@abazeed](https://wordpress.org/support/users/abazeed/)
 * I hope you’re well today!
 * Strictly speaking, a valid URL has to contain “scheme” or, at least, be “protocol-
   relative” (but that makes it impossible to know whether it actually is a website
   URL or e.g. FTP URL).
 * You can, however, disable validation and that will let visitors use addresses
   without scheme.
 * Kind regards,
    Adam
 *  Thread Starter [abazeed](https://wordpress.org/support/users/abazeed/)
 * (@abazeed)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/accept-url-that-doesnt-start-with-http-https/#post-12606784)
 * Hello [@wpmudev-support8](https://wordpress.org/support/users/wpmudev-support8/),
 * Thank you for your reply.
 * I do agree with you, but instead of disabling the validation, we can have an 
   option to bypass the scheme.
 * I tried to disable the validation but still need to use the full URL! Is it a
   bug?
 * Best Regards,
 *  Plugin Support [Dimitris – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support6/)
 * (@wpmudev-support6)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/accept-url-that-doesnt-start-with-http-https/#post-12630318)
 * Hello there [@abazeed](https://wordpress.org/support/users/abazeed/)
 * I just tested that and the Website validation doesn’t return any error if I use
   
   [http://example.com](http://example.com) or example.com
 * > I tried to disable the validation but still need to use the full URL! Is it
   > a bug?
 * Can you please let me know how you test this? As I wasn’t able to replicate.
 * Warm regards,
    Dimitris
 *  Plugin Support [Imran – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support9/)
 * (@wpmudev-support9)
 * [6 years ago](https://wordpress.org/support/topic/accept-url-that-doesnt-start-with-http-https/#post-12851198)
 * Hello [@abazeed](https://wordpress.org/support/users/abazeed/)
 * I hope you are doing well!
 * We haven’t heard back from you for a while now so we’ve marked this ticket as
   resolved. If you do have any followup questions or require further assistance
   feel free to reopen it and let us know here.
 * Kind regards,
    Nastia

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Accept URL that doesn’t start with http/https’ is closed to new replies.

 * ![](https://ps.w.org/forminator/assets/icon-256x256.gif?rev=3443182)
 * [Forminator Forms – Contact Form, Payment Form & Custom Form Builder](https://wordpress.org/plugins/forminator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/forminator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/forminator/)
 * [Active Topics](https://wordpress.org/support/plugin/forminator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/forminator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/forminator/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [Imran – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support9/)
 * Last activity: [6 years ago](https://wordpress.org/support/topic/accept-url-that-doesnt-start-with-http-https/#post-12851198)
 * Status: resolved