You declare the HTTP response code and validate the URLs against them. By Ilya Grigorik on September 07, 2006 Wouldn't it be nice if you could validate the format and the existence of a URI/URL provided by the users in your Rails application? So after a little research I put together a Code above is a barebones check which first validates the URL format against a provided regular expression ( and if it passes, it sends a HEAD (header) request and checks if we get a 200 Code (HTTPSuccess) back.So, now we can validate the format of the URL and check that the URL is alive and breathing (returns Code 200).
However, if the user only changes the name field and not the e-mail field, you do not want a validation error to be thrown because the user is already the owner of the e-mail address.
To instruct the validator to ignore the user's ID, we'll use the The field under validation must be a valid URL.
To learn about Laravel's powerful validation features, let's look at a complete example of validating a form and displaying the error messages back to the user.
First, let's assume we have the following routes defined in our object.
It is free software, and may be redistributed under the terms specified in the LICENSE file.