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
There should be an option similiar to how it's done for the response headers in #44 to pass client request headers to the server.
Use case:
User-Agent / Client IP (X-FORWARED-FOR header)
Right now our main api receives User-Agent: node and the ip-address of the node server.
Right now to achieve this, we need to create a custom route and proxy them ourselves. We cannot set client: true ,because this would expose an Authorization header that we set.
Additional information
Would you be willing to help implement this feature?
Can you think of other implementations of this feature?
Describe the feature
There should be an option similiar to how it's done for the response headers in #44 to pass client request headers to the server.
Use case:
Right now our main api receives User-Agent: node and the ip-address of the node server.
Right now to achieve this, we need to create a custom route and proxy them ourselves. We cannot set
client: true
,because this would expose anAuthorization
header that we set.Additional information
Final checks
The text was updated successfully, but these errors were encountered: