What is the correct way to implement the next query param in auth/confirm routes?
In the auth/confirm routes for Supabase UI the "next" search param is only used if it starts with
In the Supabase SSR docs it just uses it as is.
If I use the implementation from Supabase UI then it would never work because the redirect URL needs to have the full domain in it.
I don't think it would be a security issue because that URL can only ever be from the allowed URL list. Am I missing something?
/In the Supabase SSR docs it just uses it as is.
If I use the implementation from Supabase UI then it would never work because the redirect URL needs to have the full domain in it.
I don't think it would be a security issue because that URL can only ever be from the allowed URL list. Am I missing something?
