Changes between Initial Version and Version 6 of Ticket #21837


Ignore:
Timestamp:
Jan 17, 2017, 3:12:34 PM (8 years ago)
Author:
Anton Samarchyan
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21837

    • Property Cc eromijn@… added
    • Property Keywords nlsprint14 added
    • Property Owner nobody removed
    • Property Triage Stage UnreviewedAccepted
    • Property Summary auth.User Email - non-RFC spec normalizationauth.User Email - non-RFC spec case normalization
  • Ticket #21837 – Description

    initial v6  
    1 when a user signs up with Monkey@BadDomain.com
     1when a user signs up with `Monkey@BadDomain.com`
    22
    3 auth.User.object.normalize_email() saves the email as Monkey@baddomain.com to conform with RFC.
     3auth.User.object.normalize_email() saves the email as `Monkey@baddomain.com` to conform with RFC.
    44
    5 But future lookups will return None due to  BadDomain.com != baddomain.com where the user continually enters Monkey@BadDomain.com because thats what in their muscle/chrome memory.
     5But future lookups will return None due to  BadDomain.com != baddomain.com where the user continually enters `Monkey@BadDomain.com` because thats what in their muscle/chrome memory.
    66
    7 1. normalize_email is applied at the orm level, but should (also?) be applied at the Field level to help with this problem.
     71. normalize_email is applied at the ORM level, but should (also?) be applied at the Field level to help with this problem.
Back to Top