I’m currently experiencing an issue where passing a JWT token in the URL results in a 404 or page not found screen. This token is sent to the user in an email and used to mark their account as verified. The requests resolve without an issue locally however on Netlify it seems to 404.
In testing I removed the periods within the JWT and it resolves the request however, due to the lack of delineation, token is incorrect. Previously, to resolve this issue while using S3 buckets with Cloudflare, we updated DNS to direct this request back to
index.js so the router processes the token correctly.
Currently redirects for
vt subdomain are handled via an
ALIAS record in Route53
Confused how this fix would carry over to Netlify. Would I need to add a
_redirect file or does this issue exist within the Route53 DNS config?