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
In handling an incoming HTTP event, I need my handler to effectively make requests to "relative" urls, which it must do by constructing a new request URL relative to the incoming request URL. The current HTTP event only reports the subscription path that was answered, and does not include either the hostname, full request URL, or the gateway URL.
A handler is mapped to /login
The handler needs to make a request to /users
The handler receives an event in response to a request to http://my-gateway.example/xyz/login
The event should have fields for both the path: "/login" and the gatewayUrl: "http://my-gateway.example/xyz/"
The handler uses the gateway url and adds /users to make a request to http://my-gateway.example/xyz/users
The text was updated successfully, but these errors were encountered:
This is a Feature Proposal
In handling an incoming HTTP event, I need my handler to effectively make requests to "relative" urls, which it must do by constructing a new request URL relative to the incoming request URL. The current HTTP event only reports the subscription
path
that was answered, and does not include either the hostname, full request URL, or the gateway URL./login
/users
http://my-gateway.example/xyz/login
path: "/login"
and thegatewayUrl: "http://my-gateway.example/xyz/"
/users
to make a request tohttp://my-gateway.example/xyz/users
The text was updated successfully, but these errors were encountered: