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
When we return the URL as part of the response, we're really only returning the base URL and path. We don't include the query string, or any other transformations that undici may choose to make.
What I'd really really love is if we can trap the actual final URL that undici calls out to (query params and all) and return THAT value as part of the response.
The text was updated successfully, but these errors were encountered:
I had a bit of a look at this yesterday and struggled.
If we use the fetch or request functions we can add a bunch of event handlers and I suspect those will give us the full and final url and headers and stuff.
But when we call through a client, as we do, those callbacks don't seem to be available. Which is super frustrating.
In the new common http helpers, we build a bunch of arguments and then call out to undici:
When we return the URL as part of the response, we're really only returning the base URL and path. We don't include the query string, or any other transformations that undici may choose to make.
What I'd really really love is if we can trap the actual final URL that undici calls out to (query params and all) and return THAT value as part of the response.
The text was updated successfully, but these errors were encountered: