|
1 | 1 | --- |
2 | 2 | title: Configure a proxy when using the Azure SDK for .NET |
3 | | -description: Learn different ways to configure a proxy for use with the Azure SDK for .NET client libraries. |
| 3 | +description: Learn different approaches for configuring a proxy for use with the Azure SDK for .NET client libraries. |
4 | 4 | ms.topic: conceptual |
5 | 5 | ms.custom: devx-track-dotnet, engagement-fy23 |
6 | 6 | ms.date: 11/15/2024 |
@@ -31,18 +31,19 @@ Using the Azure Key Vault Secrets library as an example, you'd have the followin |
31 | 31 |
|
32 | 32 | The following table provides an inventory of environment variables that can be set to configure a proxy for use. |
33 | 33 |
|
34 | | -| Environment variable | Purpose | |
35 | | -|----------------------|--------------------------------------------------------------------------------------------------------------| |
36 | | -| `HTTP_PROXY` | The proxy server used on HTTP requests. | |
37 | | -| `HTTPS_PROXY` | The proxy server used on HTTPS requests. | |
38 | | -| `ALL_PROXY` | The proxy server used for both HTTP and HTTPS requests, in case `HTTP_PROXY` or `HTTPS_PROXY` are undefined. | |
39 | | -| `NO_PROXY` | A comma-delimited list of hostnames to exclude from proxying. | |
40 | | -| `GATEWAY_INTERFACE` | Set if running in a CGI environment. Example value: `CGI/1.1` | |
| 34 | +| Environment variable | Purpose | |
| 35 | +|----------------------|-------------------------------------------------------------------------------------------------------------| |
| 36 | +| `HTTP_PROXY` | The proxy server used on HTTP requests. | |
| 37 | +| `HTTPS_PROXY` | The proxy server used on HTTPS requests. | |
| 38 | +| `ALL_PROXY` | The proxy server used for both HTTP and HTTPS requests. | |
| 39 | +| `NO_PROXY` | A comma-delimited list of hostnames to exclude from proxying. | |
| 40 | +| `GATEWAY_INTERFACE` | Indicator that the app is running in a Common Gateway Interface (CGI) environment. Example value: `CGI/1.1` | |
41 | 41 |
|
42 | 42 | Be aware of the following behaviors: |
43 | 43 |
|
44 | 44 | - Each environment variable in the preceding table, except `GATEWAY_INTERFACE`, can alternatively be defined as lowercase. For example, `http_proxy`. The lowercase form takes precedence over the uppercase form. |
45 | 45 | - If both `http_proxy` and `GATEWAY_INTERFACE` are undefined, `HTTP_PROXY` is used. |
| 46 | +- `ALL_PROXY` is considered only when either an HTTP or an HTTPS proxy is undefined. |
46 | 47 | - Protocol-specific environment variables take precedence over `ALL_PROXY`. |
47 | 48 |
|
48 | 49 | The proxy server URL takes the form `http[s]://[username:password@]<ip_address_or_hostname>:<port>/`, where the `username:password` combination is optional. To get the IP address or hostname, port, and credentials for your proxy server, consult your network administrator. |
|
0 commit comments