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 page details the `ProxyConfig` class, which is used to configure HTTP proxy settings for both REST-based and gRPC-based clients."],["The `ProxyConfig` class allows setting the hostname, port, username, password, and scheme for the HTTP proxy, with the scheme defaulting to `https`."],["The full URI for the proxy is constructed dynamically as `{scheme}://{username}:{password}@{hostname}:{port}`, where empty values, excluding the scheme, are omitted."],["Modifiers are available for each field (hostname, port, username, password, scheme) via the `set_` functions that return either a `ProxyConfig&` or `ProxyConfig&&` object depending on the context."],["The document also lists all the available library versions for this class ranging from version 2.10.1 up to the latest release candidate version 2.37.0-rc."]]],[]]
