I have a Next.js webapp, with app router, and am using firebase auth. firebase auth can only refresh cookies on the client side.

The issue is that server side components fetch first, using whatever cookie is available. If the cookie is expired, the fetch will fail on server side, before client side can render and refresh the cookies.

To work around this issue I found a SO thread suggesting a redirect to a client page with just a component that refreshes the token on load and sets the cookie.

Ideally the refresh page should then redirect back to the page the user was at.
How do I get the pathname on server side so I can give it to the refresh page which will redirect back?

Please let me know if any more information is required 🙏🏼

check headers https://github.com/vercel/next.js/issues/43704#issuecomment-1949887755
next-url should have contain url

Thank you! I've tried that but

import { headers } from "next/headers";
...
    const heads = headers();
    const encodedPath = heads.get('next-url')

always gives me null

https://github.com/vercel/next.js/issues/43704#issuecomment-1956543431
this comment in that thread few comments down discourages its use

still you need to check all of headers not only next-url, and maybe bug already fixed.
otherwise only workaround with middleware either client components that will get url and pass it somewhere