Opened 11 years ago
Last modified 8 years ago
#21837 new Bug
auth.User Email - non-RFC spec normalization — at Initial Version
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | contrib.auth | Version: | 1.6 |
| Severity: | Normal | Keywords: | authentication, email, filter, get, error nlsprint14 |
| Cc: | FunkyBob, eromijn@… | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description ¶
when a user signs up with Monkey@…
auth.User.object.normalize_email() saves the email as Monkey@… to conform with RFC.
But future lookups will return None due to BadDomain.com != baddomain.com where the user continually enters Monkey@… because thats what in their muscle/chrome memory.
- normalize_email is applied at the orm level, but should (also?) be applied at the Field level to help with this problem.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR].
Note:
See TracTickets
for help on using tickets.