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 SoftLayer (and other cloud environments I suspect), all our outbound connections goes through a forward proxy, so this look up being an outbound call, needs to go thru that fwd proxy. Furthermore, in our case we read the proxy values from a DB at runtime. Consequently, we need a way to pass the proxy host, port, username and password to the smp-client on the lookup call which would then be used to make the http connection.
Finally, we have multiple environments with different requirements. Some are internal only and don't use a proxy, some use a proxy, but don't require userid and password, and some require the proxy and the userid/password. It would be nice if the lookup ignores any parameters that have a null value, for example the proxy host and port could be present with some values, whereas username and password might not there there..so it should just use the proxy host and port in that case.
The text was updated successfully, but these errors were encountered:
HI,
I am currently in the middle of setting up the Customer Test Environment
for our new access point. I will test it as soon as I finish that.
Thanks for adding that feature.
In SoftLayer (and other cloud environments I suspect), all our outbound connections goes through a forward proxy, so this look up being an outbound call, needs to go thru that fwd proxy. Furthermore, in our case we read the proxy values from a DB at runtime. Consequently, we need a way to pass the proxy host, port, username and password to the smp-client on the lookup call which would then be used to make the http connection.
Finally, we have multiple environments with different requirements. Some are internal only and don't use a proxy, some use a proxy, but don't require userid and password, and some require the proxy and the userid/password. It would be nice if the lookup ignores any parameters that have a null value, for example the proxy host and port could be present with some values, whereas username and password might not there there..so it should just use the proxy host and port in that case.
The text was updated successfully, but these errors were encountered: