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."],[[["This webpage details the `ProxyConfig` class, used for configuring HTTP proxies for REST and gRPC-based clients."],["The latest version available for `ProxyConfig` is `2.37.0-rc`, with many prior versions also listed, including versions going as far back as `2.10.1`."],["The `ProxyConfig` class allows users to set parameters such as hostname, port, username, password, and scheme, which are used to construct the full proxy URI."],["If the hostname value is not set, then the HTTP proxy is not configured, and the scheme will default to `https` if not explicitly defined."],["There are various functions for modifying the configurations of the class, such as `set_hostname`, `set_port`, `set_username`, `set_password`, `set_scheme`, as well as functions to retrieve such values like `hostname()`, `port()`, `username()`, `password()`, and `scheme()`."]]],[]]
