Open stevebeauge opened 2 years ago
The original url is dropped (since request is replaced). You can however write a middleware and push that info in the outgoing request probably?
Let me know if this helps
Thanks for the suggestion. I tried to write a plugin, but unfortunately, plugin has no access (as far as I know) to the incoming relayed request.
The incoming Path and Query are same unless you add a prefix to it, so your plugin can make those assumptions if you do not intend to make it super generic.
Other option would be to load appSettings.json and read redirectionUrl
and hybridConnectionUrl
from it. Compare it with Path and Query of outgoing request to service running locally. That should give you information about the original url.
I'm prototyping this tools and it looks far more reliable than other free tunneling tools I tested.
However, I need to dynamically know what the exposed endpoint. When the local server get the request, the
host
header islocalhost
.I can there is a
via
header, but it only contains the relay host url, not the full url.Is there any way to retrieve the original url ?
FYI, here's the details of my setup:
https://my-relay-namespace.servicebus.windows.net:443/mycomputername
http://localhost:7071
via
header :1.1 my-relay-namespace.servicebus.windows.net
.The service behind 7071 port is the local azure function host emulator.
Is use this to implement some SharePoint Addins and the exact exposed url is important because of some callback urls returned by the function. I may add the url as part of the function settings, but it would simplier I guess to just get the actual URL from, why not, a TunnelRelay specific header ?