Okay, I edited the original post with a couple of improvements. Added support for !()
. Combined the path/query stuff. And disallow http://.www
.
Feel free to make suggestions. I obviously don’t restrict what can come before the URL, maybe that is something that is important. Maybe a simple \b
at the beginning would be fine. Maybe urls that contain unicode would be desired etc. I guess that the is real point, a regex’s quality is measured by your use case.
I mean, you can go crazy with something like this I found online:
_^(?:(?:https?|ftp)://)(?:\S+(?::\S*)?@)?(?:(?!10(?:\.\d{1,3}){3})(?!127(?:\.\d{1,3}){3})(?!169\.254(?:\.\d{1,3}){2})(?!192\.168(?:\.\d{1,3}){2})(?!172\.(?:1[6-9]|2\d|3[0-1])(?:\.\d{1,3}){2})(?:[1-9]\d?|1\d\d|2[01]\d|22[0-3])(?:\.(?:1?\d{1,2}|2[0-4]\d|25[0-5])){2}(?:\.(?:[1-9]\d?|1\d\d|2[0-4]\d|25[0-4]))|(?:(?:[a-z\x{00a1}-\x{ffff}0-9]+-?)*[a-z\x{00a1}-\x{ffff}0-9]+)(?:\.(?:[a-z\x{00a1}-\x{ffff}0-9]+-?)*[a-z\x{00a1}-\x{ffff}0-9]+)*(?:\.(?:[a-z\x{00a1}-\x{ffff}]{2,})))(?::\d{2,5})?(?:/^\s]*)?$_iuS
But I think I was just looking for something that worked well enough in my particular use cases.