Fixed the fix from [7775].

The previous change was failing Django's "check for well-formed domain name"
validation, rather than failing on the network side. Providing we don't ever
set up www.broken.djangoproject.com as a valid domain name, this change should
let us control our own destiny.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@7776 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2008-06-28 10:55:26 +00:00
parent 40d2b419ab
commit be6ff148c1
2 changed files with 2 additions and 2 deletions

View File

@ -237,7 +237,7 @@ ValidationError: [u'REQUIRED']
Traceback (most recent call last): Traceback (most recent call last):
... ...
ValidationError: [u'INVALID'] ValidationError: [u'INVALID']
>>> f.clean('http://www.test.invalid') >>> f.clean('http://www.broken.djangoproject.com')
Traceback (most recent call last): Traceback (most recent call last):
... ...
ValidationError: [u'INVALID LINK'] ValidationError: [u'INVALID LINK']

View File

@ -887,7 +887,7 @@ u'http://www.google.com'
Traceback (most recent call last): Traceback (most recent call last):
... ...
ValidationError: [u'Enter a valid URL.'] ValidationError: [u'Enter a valid URL.']
>>> f.clean('http://www.test.invalid') # bad domain >>> f.clean('http://www.broken.djangoproject.com') # bad domain
Traceback (most recent call last): Traceback (most recent call last):
... ...
ValidationError: [u'This URL appears to be a broken link.'] ValidationError: [u'This URL appears to be a broken link.']