Full Request URL Data

[Crisfole]

Describe the problem

I redirect users to external auth providers that accept a redirect url as a query parameter. In order to do this from a hook I need to rebuild the url by combining the various pieces by hand and some environment information to determine protocol. This is inconvenient and doesn't easily allow using the platform.

Describe the proposed solution

I'd like a url: URL property on the ServerRequest. It does mean all the adapters need tweaking, but it feels like a reasonable need for a web server.

Alternatives considered

Building the full URL by hand.

Importance

would make my life easier

Additional Information

No response

[mohamadHarith]

Hi Crisfole, you can get the entire URL of the page that makes the request from the headers using the request.headers.referer. Please see the attached image below.

[zyxd]

Unfortunately, request.headers.referer may not be defined, depending on the situation. The protocol is difficult to determine, since the application can work through a proxy, docker, etc.

It might be better to use a predefined environment variable with a URL like Vercel and Netlify do.

[Crisfole]

Referrer is also supposed to be the url of the referring site, nut the current one...

[Rich-Harris]

This will be fixed by #3126