Set up proxies to be used by tests to ensure client libraries can connect through...proxies...

[johanste]

Azure/azure-sdk#175 tracks the requirement for client libraries to be able to connect through proxies. Just as it is a common requirement to support it, it is also a common requirement to verify said support. Having proxies that are set up to use auth (digest and basic) would presumably be needed for this.

[johanste]

FYI: @bterlson, @mssfang

[mikeharder]

One idea I had:

1. Run HTTP proxy in a docker container.
2. Run tests in docker container with no outbound internet and only access to proxy container.
3. Run tests, verify access through proxy works and direct access fails.

[kurtzeborn]

@JimSuplizio, pretty sure this very old issue is covered by the work you're planning to do with recordings. Feel free to reword/fix/close this issue as you see fit and as it aligns with the recording epic you're working on.

[scbedd]

I will transfer this issue to sdk-tools and apply label to it. Test-proxy definitely supports this scenario if the policies on client side are set up properly.

The way it should work is

• Request with original URI.
• core package detects presence of HTTP_PROXY environment variable and updates target URI/headers.
• Test-proxy policy applies last and updates the already updated target URI/headers to route to test proxy.
• Test-proxy makes request to the proxy server, records result as normal.

[scbedd]

Closing, this is client side.