Timeline for Regex to parse URLs for their correctness according to RFC 3986

7 events

when toggle format	what		by	license	comment
May 16, 2016 at 9:06	comment	added	Krishna Chaitanya		Finally, this is the regex. Tested against all the examples in RFC
May 13, 2016 at 14:32	comment	added	BCdotWEB		Please follow these instructions to merge your multiple accounts: codereview.stackexchange.com/help/merging-accounts
May 13, 2016 at 13:47	comment	added	dot_Sp0T		The above comment refers to the phrasing: `Even I need a foolproof regex to validate URI entered by users.` found in your answer. I interpreted the phrasing as you needing a regex to parse URIs, thus I took the time to write the extensive comment
May 13, 2016 at 13:43	comment	added	dot_Sp0T		Indeed. The regex in my question and the whole question is actually about URLs (which are a form of absolute URIs). Back when I wrote the question the difference didn't seem to be there, but I also learned lots of things in the meantime. I'll update the phrasing in the question to point that out.\|\| On the other hand to solve your issue, just take the subregex validating the schema from above (slightly modify it) and append `.*`. As follows: `[A-Za-z][A-Za-z0-9+.-]+:.+` <- this should match the simplest form of URI possible and thus every more complex form as well - hth
May 13, 2016 at 13:42	review	Late answers
May 13, 2016 at 14:08
May 13, 2016 at 13:27	review	First posts
May 13, 2016 at 14:35
May 13, 2016 at 13:23	history	answered	Krishna Chaitanya	CC BY-SA 3.0