-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magic links break when Outlook safe links are enabled #189
Comments
I've googled a bit and seems to be a common issue.
In summary, I think there are two solutions:
If we could try solution 1. and check if it works I think that would be the cleanest solution for now. |
@elitan Did that actually fix the problem? I’m in a similar situation now, and from what I gather reading a lot of issues and tickets all around, it shouldn't have worked? |
I think it was fixed yes. Did you experience something else? |
I haven’t really tried it out yet, but I was asking due to comments such as the ones on this StackOverflow issue, where disabling HEAD requests was said to not work. However, returning a smile and a thumbs up like your fix here might work [differently]. |
Unfortunately, this solution no longer works. In my testing, Outlook makes actual GET requests during its link scanning, not just HEAD requests. |
I've got the same problem with magic links. Links are invalid before the user got the chance to click it. |
We wrote about this issue recently: https://nhost.io/blog/protect-magic-links-from-email-clients |
Magic links don't work from Outlook when safe links are enabled.
The logs show that the verifyHandler is called multiple times when the link is clicked (as part of the safety check) - the first time the ticket is removed from the user record and redirect is called correctly, but this is cancelled out by the subsequent calls to verifyHandler where the ticket no longer exists and an error response is sent.
The code where this happens is here:
hasura-auth/src/routes/verify/verify.ts
Lines 33 to 62 in 9f5cbbc
The text was updated successfully, but these errors were encountered: