skip to content »

Javascript validating url

javascript validating url-33

I also don’t want to allow every possible technically valid URL — quite the opposite.

javascript validating url-43

\$&'\(\)\*\ ,;=]|:|@)*)*)|((([a-z]|\d|-|\.|_|~|[\x00A0-\x D7FF\x F900-\x FDCF\x FDF0-\x FFEF])|(%[\da-f])|[! ((([a-z]|\d|-|\.|_|~|[\x00A0-\x D7FF\x F900-\x FDCF\x FDF0-\x FFEF])|(%[\da-f])|[! Also, single weird leading and/or trailing characters aren’t tested for. Just imagine you’re doing this before testing modifier to all the regexes to speed up the tests. Here’s a plain text list of all the URLs used in the test. $/i.test(value); // Copyright (c) 2010-2013 Diego Perini, MIT licensed // // see also // modified to allow protocol-relative URLs return this.optional( element ) || /^(? :[a-z\u00a1-\uffff0-9]-*)*[a-z\u00a1-\uffff0-9] )(? Assume that this regex will be used for a public URL shortener written in PHP, so URLs like shouldn’t pass (even though they’re technically valid).

Also, in this case I only want to allow the HTTP, HTTPS and FTP protocols. :ac|ad|aero|ae|af|ag|ai|al|am|an|ao|aq|arpa|ar|asia|as|at|au|aw|ax|az|ba|bb|bd|be|bf|bg|bh|biz|bi|bj|bm|bn|bo|br|bs|bt|bv|bw|by|bz|cat|ca|cc|cd|cf|cg|ch|ci|ck|cl|cm|cn|coop|com|co|cr|cu|cv|cx|cy|cz|de|dj|dk|dm|do|dz|ec|edu|ee|eg|er|es|et|eu|fi|fj|fk|fm|fo|fr|ga|gb|gd|ge|gf|gg|gh|gi|gl|gm|gn|gov|gp|gq|gr|gs|gt|gu|gw|gy|hk|hm|hn|hr|ht|hu|id|ie|il|im|info|int|in|io|iq|ir|is|it|je|jm|jobs|jo|jp|ke|kg|kh|ki|km|kn|kp|kr|kw|ky|kz|la|lb|lc|li|lk|lr|ls|lt|lu|lv|ly|ma|mc|md|me|mg|mh|mil|mk|ml|mm|mn|mobi|mo|mp|mq|mr|ms|mt|museum|mu|mv|mw|mx|my|mz|name|na|nc|net|ne|nf|ng|ni|nl|no|np|nr|nu|nz|om|org|pa|pe|pf|pg|ph|pk|pl|pm|pn|pro|pr|ps|pt|pw|py|qa|re|ro|rs|ru|rw|sa|sb|sc|sd|se|sg|sh|si|sj|sk|sl|sm|sn|so|sr|st|su|sv|sy|sz|tc|td|tel|tf|tg|th|tj|tk|tl|tm|tn|to|tp|travel|tr|tt|tv|tw|tz|ua|ug|uk|um|us|uy|uz|va|vc|ve|vg|vi|vn|vu|wf|ws|xn--0zwm56d|xn--11b5bs3a9aj6g|xn--80akhbyknj4f|xn--9t4b11yi5a|xn--deba0ad|xn--g6w251d|xn--hgbk6aj7f53bba|xn--hlcj6aya9esc7a|xn--jxalpdlp|xn--kgbechtv|xn--zckzah|ye|yt|yu|za|zm|zw)|(?

Server side validation is performed by a web server, after input has been sent to the server.

Client side validation is performed by a web browser, before input is sent to a web server.

(I don't know of one for Java Script; it would probably be overkill. If you get a 404 or connection error, it's probably wrong. If you want to check whether a hostname such as ‘wwww’ actually exists, you have no choice but to look it up in the DNS. I written also a URL validation function base on rfc1738 and rfc3986 to check http and https urls. (((25[0-5]|2[0-4][0-9]|[0-1][0-9][0-9]|[1-9][0-9]|[0-9])(\.(25[0-5]|2[0-4][0-9]|[0-1][0-9][0-9]|[1-9][0-9]|[0-9])))|localhost|([a-z A-Z0-9\-\u00C0-\u017F] \.) ([a-z A-Z]))(:[0-9] )?

Certainly your current expression fails many valid URLs, and passes invalid ones. use a proper URL parser that actually follows the real rules. just trim away any leading or trailing spaces, then check it has one of your preferred schemes on the front (typically ‘ or ‘https://’), and leave it at that. attempt to use the URL and see what lies at the end, for example by sending it am HTTP HEAD request from the server-side.

So I suggest you read the API to perform more checks, for example if you want to make sure that the user entered a well formed absolute URL you may do like this: If i test this:---- /^(ftp|http|https):\/\/(\w :\w*@)?