Netlify-Redirects drops Netlify-Identity confirmation token (URL Hash Values)

Yep — I’ll corroborate this as Colin and I have been working together on his site a bit (he’s implementing my gatsby-plugin-netlify-identity-gotrue plugin that interfaces to GoTrue / Netlify Identity. The terminal above is mine too :laughing: but indeed, the confirmation token URL passed back from GoTrue via Mandrill is in the format of Example Domain and (I wonder if related to Changes to Redirects with query string parameters are coming) the #confirmation_token=123a bit is getting dropped in the redirection. Since it’s in the hash section of the URL and not technically a query-string parameter, I think it’s just getting chopped off :confused: which, in this case, where all users from the US are redirected to path-prefix /id/, means that nobody in the US, ID, or MX can actually confirm their account or execute any other token-based Netlify Identity actions :frowning:

I’ll go ahead and tag @fool in to see if he’s got any ideas on it :slight_smile:


Jon