#24832: URLField validation isn't very strict
----------------------------------------------+--------------------
Reporter: knyghty | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
When getting a URL from twitter and putting it in the database, I
accidentally got all the URLs instead of just the one I wanted, and stored
it directly in the database, as json:
{'display_url': 'bbc.in/1dkGEkp', 'expanded_url': 'http://bbc.in/1dkGEkp',
'url': 'http://t.co/gnpLjnnOC8', 'indices': [88, 110]}.
I didn't get any errors along the way, and it stored it just fine.
I'm not sure if it's intentional that the validator is lax here - the docs
don't really specify if the URL has to be valid - but I thought I'd best
report it in any case.
--
Ticket URL: <https://code.djangoproject.com/ticket/24832>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.c288beb9badb913f40193789ee478a22%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
