2022.2 http client env variables changed/broken?


Works fine in 2022.1 -  tried out 2022.2. and it doesn't seem to work.

It'll warn that the variable is not set if I use the wrong name, but when I run it - it appears to send the variable name instead of the value.

1 comment
Comment actions Permalink

Can you please provide a small example showing the problem?


Please sign in to leave a comment.