URL Validation: Add support for other schemes apart from https, http, ftp

[dvignacioglobal]

Given in the documentation link, the validator does not return True if I use a different scheme such as rtmp or rtsp.

  foo://admin:hunter1@example.com:8042/over/there?name=ferret#nose
  \_/   \___/ \_____/ \_________/ \__/\_________/ \_________/ \__/
   |      |       |       |        |       |          |         |
scheme username password hostname port    path      query    fragment

An example of this is

rtmp://192.168.1.123:1935/live/test

If I run this code:

import validators

streamurl = "rtmp://192.168.1.123:1935/live/test"
print(validators.url(streamurl))

The output is:

ValidationError(func=url, args={'value': 'rtmp://192.168.1.123:1935/live/test'})

It would be nice if the URL validator supports other schemes. Thanks.

[yozachar]

"ftp", "ftps", "git", "http", "https",
"rtmp", "rtmps", "rtsp", "sftp",
"ssh", "telnet",

Apart from these, do you have any other protocols in mind that follows a similar scheme://netloc/path;parameters?query#fragment syntax?

[dvignacioglobal]

Thanks for replying! I have nothing more to add to the list.

[nyuware]

Opening the issue again, would it be possible to parse all the available schemes from IANA available here instead of hardcoding a list ? Like it's already being done for the TLDS Thanks!

[yozachar]

parse all the available schemes from IANA

Would be impractical. Hence to cover as much as possible #352 exists.

[tofetpuzo]

is this feature still live?

[yozachar]

is this feature still live?

What are you referring to specifically?

[tofetpuzo]

is this feature still live?

What are you referring to specifically?

Hey @yozachar here -> "feature add non-exhaustive Url validation"

[yozachar]

is this feature still live?

What are you referring to specifically?

Hey @yozachar here -> "feature add non-exhaustive Url validation"

Yes