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 proxies 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 HTTPS being the default scheme."],["The full proxy URI is constructed using the provided scheme, username, password, hostname, and port, and empty values are omitted except for the scheme, and if the hostname is empty, no proxy is set."],["The document details a constructor and modifier functions to set the various values to set the proxy, as well as functions to retrieve the set values."],["This page provides documentation of versions 2.10.1 to 2.37.0-rc of `ProxyConfig`."]]],[]]
