'Email confirm' validation should not be case sensitive

Created on 9 September 2019, over 5 years ago
Updated 3 April 2025, 10 days ago

For email clients there's no difference between User@email.com and user@email.com or USER@EMAIL.COM.
Following this, I believe that 'email confirm' validation should not be case sensitive.

📌 Task
Status

Closed: won't fix

Version

5.4

Component

Code

Created by

🇬🇧United Kingdom Vlad Stratulat London

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇦Canada colan Toronto 🇨🇦

    I think it is an edge case that someone would intentionally enter in the same email address using different cases.

    True.

    The issue is not about modifying user's data, its about validation.

    Also true.

    What hasn't been mentioned here is that the part before the "@" could be case sensitive if mail servers are configured that way (see discussion), even though it's silly. So leaving this closed for that reason isn't crazy.

    However, if I were to post a patch here, I'd be using strcasecmp(), not strtolower(). 😉

Production build 0.71.5 2024