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 outlines 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 variety of previous versions from 2.36.0 all the way down to 2.10.1 available, all with documentation."],["The `ProxyConfig` class allows users to define the hostname, port, username, password, and scheme for an HTTP proxy."],["The full URI is constructed dynamically, omitting empty values except for the `scheme` which defaults to `https`, and if `hostname` is empty no HTTP proxy will be configured."],["The `set_` methods allows for setting the values of the configuration and are defined for `hostname`, `port`, `username`, `password` and `scheme`, both as a `&` and a `&&`, while the `_()` methods are for accessing them."]]],[]]
