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
which results in a snippet which is able to be parsed. However, it seems to interpret the argument as the schema instead of the port, so it will proxy urls from 80://127.0.0.1 instead of 127.0.0.1:80.
I'm wondering if there's a way to use both the upstreams template and snippet arguments at the same time?
I'm trying to write a snippet which takes in an argument and passes it as the port to the upstreams template. I've tried a few variations:
this errors encountering an unexpected '{' character and the snippet was not able to be parsed.
Next I tried
which results in a snippet which is able to be parsed. However, it seems to interpret the argument as the schema instead of the port, so it will proxy urls from
80://127.0.0.1
instead of127.0.0.1:80
.I'm wondering if there's a way to use both the upstreams template and snippet arguments at the same time?
The result I want is
as I'm proxying to an https endpoint.
The text was updated successfully, but these errors were encountered: