#33456: Make underscore in hostname error more explicit
-------------------------------------+-------------------------------------
Reporter: kimsia | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: HTTP handling | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by kimsia):
> Is this really Django's choice? 🤔 As far as I'm aware they are
forbidden in RFC 1035 and we're not doing anything unusual here.
I mean yes, it's Django's choice to follow RFC 1035 strictly. I have no
issues with that.
The more explicit message for underscore is to help silly people like me
to realize the error faster.
To address the issue of not treating underscore any more special, would
you mind if I change the error message to highlight which character
doesn't conform to the hostname regardless whether it's underscore or
something else.
--
Ticket URL: <https://code.djangoproject.com/ticket/33456#comment:3>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.0d94b334f5e45f701d015b6ca1a40cfd%40djangoproject.com.
