This configuration can be used for both REST-based and gRPC-based clients. The client library sets the underlying configuration parameters based on the values in this struct.
The full URI is constructed as:
{scheme}://{username}:{password}hostname}:{port}
Any empty values are omitted, except for the scheme which defaults to https. If the hostname value is empty, no HTTP proxy is configured.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["The document details the `ProxyConfig` class, which is used to configure HTTP proxy settings for both REST-based and gRPC-based clients."],["The latest version of `ProxyConfig` is 2.37.0-rc, with a history of versions dating back to 2.10.1 available."],["The `ProxyConfig` class allows setting parameters like hostname, port, username, password, and scheme for the HTTP proxy."],["The full URI for the proxy is constructed using the format `{scheme}://{username}:{password}hostname}:{port}`, with `https` being the default scheme."],["If the `hostname` value is empty, no HTTP proxy will be configured by the client."]]],[]]
