When I'm using @supabase/ssr, and establish a session in a client browser, then use a server action in my Next.js application, there is no way to pass the client's IP to Supabase.
For example, when I'm using a browser-side client, the IP is visible in the X-Real-IP header, because the client is connecting directly to the Supabase backend. I can confirm that in the Edge API log browser.
But when I want to run a server action, the connection is now client->Next.js server->Supabase. This extra step loses track of the IP and I see no way to pass it along. The IP displayed in the logs is actually the AWS IP that my Next.js application is running on.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Create a Next.js application and add @supabase/ssr.
Setup the package according to the instructions in the docs.
Write a simple server action, for example for fetching anything from the database.
Perform the action.
Go to the logs in Supabase, and inspect the GET request.
Expected behavior
I'd expect an extra X-something header that would contain the client's actual IP.
Bug report
Describe the bug
When I'm using @supabase/ssr, and establish a session in a client browser, then use a server action in my Next.js application, there is no way to pass the client's IP to Supabase.
For example, when I'm using a browser-side client, the IP is visible in the X-Real-IP header, because the client is connecting directly to the Supabase backend. I can confirm that in the Edge API log browser.
But when I want to run a server action, the connection is now client->Next.js server->Supabase. This extra step loses track of the IP and I see no way to pass it along. The IP displayed in the logs is actually the AWS IP that my Next.js application is running on.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
I'd expect an extra X-something header that would contain the client's actual IP.
ScreenshotsN/A
System information