You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an email conatins a + like in name+something@email.com which is a valid email, the final email saved is without the + (name something@email.com).
This is because when the callback is visited this is the url http://localhost:7000/api/auth/callback/email?email=name+something@email.com&token=72544&callbackUrl=http://localhost:7000/. As you can see the email is not encoded correctly and the + get lost
Is this a bug in your own project?
No
How to reproduce ☕️
Just use an email with +. If you have a gmail account you can use youremail+whatever@gmail.com
Description 🐜
When an email conatins a
+
like inname+something@email.com
which is a valid email, the final email saved is without the+
(name something@email.com
).This is because when the callback is visited this is the url
http://localhost:7000/api/auth/callback/email?email=name+something@email.com&token=72544&callbackUrl=http://localhost:7000/
. As you can see the email is not encoded correctly and the+
get lostIs this a bug in your own project?
No
How to reproduce ☕️
Just use an email with
+
. If you have a gmail account you can useyouremail+whatever@gmail.com
Screenshots / Logs 📽
No response
Environment 🖥
System:
OS: Linux 5.8 KDE neon 5.22
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 1.65 GB / 15.51 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 14.17.2 - /usr/bin/node
Yarn: 1.22.10 - ~/.npm-global/bin/yarn
npm: 6.14.13 - /usr/bin/npm
Browsers:
Brave Browser: 91.1.26.74
Chrome: 91.0.4472.114
Firefox: 89.0.2
npmPackages:
next: ^11.0.0 => 11.0.1
next-auth: ^3.27.3 => 3.27.3
react: ^17.0.2 => 17.0.2
Contributing 🙌🏽
Yes, but I need you to point me in the right direction
The text was updated successfully, but these errors were encountered: