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
Hi all,
I am sitting on this issue for days now, maybe one of you can make sense of it:
I'm trying to use a redirect in a server sided function. It is part of an auth flow, basically the user clicks 'send' on a form on the login page, this is triggering a 'signInWithAzure' function with the "use server" keyword. This function builds a url to my auth container (supabase auth) and redirects to it but the redirect is not executed in the browser.
I can see in the logs that the url is generated, i can see in the browser network tools that the response from the server to the login button is containing the 'X-Action-Redirect' Header with the correct url but the browser/client does not act on it. No error, no loading, no outgoing request, just nothing.
The strange thing is that it works locally but not deployed on gke. But since the browser receives the response with the redirect header but does no further request I deducted that the issue is really on the client side, so no GKE/Supabase auth/Container config should be involved.
One factor that i could imagine is that the redirect is going from baseurl/de/login to baseurl/gateway/auth/v1/authorize which is routed by the cluster to the supabase auth container and not the nextjs app. So to the app it might look like an internal redirect (same baseurl) but it actually isn't.
Could it be connected to this bug? I am no frontend dev so I don't yet fully understand the bug report but it looks similar.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
Hi all,
I am sitting on this issue for days now, maybe one of you can make sense of it:
I'm trying to use a redirect in a server sided function. It is part of an auth flow, basically the user clicks 'send' on a form on the login page, this is triggering a 'signInWithAzure' function with the "use server" keyword. This function builds a url to my auth container (supabase auth) and redirects to it but the redirect is not executed in the browser.
I can see in the logs that the url is generated, i can see in the browser network tools that the response from the server to the login button is containing the 'X-Action-Redirect' Header with the correct url but the browser/client does not act on it. No error, no loading, no outgoing request, just nothing.
The strange thing is that it works locally but not deployed on gke. But since the browser receives the response with the redirect header but does no further request I deducted that the issue is really on the client side, so no GKE/Supabase auth/Container config should be involved.
One factor that i could imagine is that the redirect is going from
baseurl/de/login
tobaseurl/gateway/auth/v1/authorize
which is routed by the cluster to the supabase auth container and not the nextjs app. So to the app it might look like an internal redirect (same baseurl) but it actually isn't.Could it be connected to this bug? I am no frontend dev so I don't yet fully understand the bug report but it looks similar.
This is my function and the response headers:
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions