overly agressive URLField validation causes failures
Bug #1528710 reported by
LaMont Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Django |
Unknown
|
Unknown
|
|||
python-django (Debian) |
Fix Released
|
Unknown
|
|||
python-django (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If the django site lives somewhere that the admins have declared a bogus top-level domain, and chosen to use an rfc1035-conforming name (with a hyphen in the middle of it), then django URLField validation considers the domain to be invalid. (I suspect that IANA hasn't released any TLDs with hyphens yet - making them the ideal choice right now for "something that won't be real".)
That is to say: http://
Please fix the validator to allow hyphens in the tld_re.
lamont
Changed in python-django (Debian): | |
status: | Unknown → Confirmed |
Changed in python-django (Ubuntu): | |
status: | Confirmed → In Progress |
assignee: | nobody → LaMont Jones (lamont) |
Changed in python-django (Debian): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
This does appear to be a regression.
This is a change that only took effect in Django 1.8, if I understand correctly.
There's a related ticket <https:/ /code.djangopro ject.com/ ticket/ 25452#comment: 2> and I had a brief discussion about this on #django-dev; please do feel free to file a ticket against upstream and a patch can probably be backported. I'd prefer to see it fixed in Django upstream first, though.