Re: Invalid URLs passing validation by URLValidator

2018-06-27 Thread Tim Bell
On Friday, 22 June 2018 20:53:54 UTC+10, Jason wrote: > > Interesting find.. the only time I've used that kind of URL convention is > by connecting to redis with the python redis library. It also fits db url > connection strings too. > > What's the actual use case for the URL schema? > The us

Re: Invalid URLs passing validation by URLValidator

2018-06-27 Thread Tim Bell
Just picking up on a few points... On Friday, 22 June 2018 21:51:01 UTC+10, Melvyn Sopacua wrote: > > > However, officially, HTTP urls do not allow for username and password as > outlined in section 3.3: > > > > An HTTP URL takes the form: > > > http://:/? > > > where and are as des

Re: Invalid URLs passing validation by URLValidator

2018-06-22 Thread Melvyn Sopacua
On vrijdag 22 juni 2018 02:50:08 CEST Tim Bell wrote: > http://#FOO#/b...@example.com > > I believe that this is passing validation because "#FOO#/bar" is being > treated as a username, with "example.com" as the hostname. However, > "#FOO#/bar" shouldn't be valid as a username because the "#" and

Re: Invalid URLs passing validation by URLValidator

2018-06-22 Thread Jason
Interesting find.. the only time I've used that kind of URL convention is by connecting to redis with the python redis library. It also fits db url connection strings too. What's the actual use case for the URL schema? You could also report this to the https://groups.google.com/forum/#!forum/

Invalid URLs passing validation by URLValidator

2018-06-21 Thread Tim Bell
Hi, I've come across some strings which I think aren't valid URLs that nevertheless pass validation by django.core.validators.URLValidator in Django 2.0.6 and 1.11.13. I know URL validation is very tricky, but these seemed to me that they should obviously fail. http://#FOO#/b...@example.com I