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 document details the `ProxyConfig` class, which is used to configure HTTP proxies for both REST and gRPC clients."],["The `ProxyConfig` class allows setting the hostname, port, username, password, and scheme for the proxy, with the scheme defaulting to `https`."],["The full URI for the proxy is constructed using the provided scheme, username, password, hostname, and port, omitting any empty values except for the scheme."],["The latest version of the `ProxyConfig` class is version 2.37.0-rc, and there are also multiple previous versions detailed all the way down to 2.10.1."],["This class has multiple modifiers to allow the setting of each part of the proxy address, using `set_hostname`, `set_port`, `set_username`, `set_password`, and `set_scheme`, and also has a getter for each, respectively `hostname`, `port`, `username`, `password`, and `scheme`."]]],[]]
