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 `ProxyConfig` class allows setting parameters such as hostname, port, username, password, and scheme to define the HTTP proxy, with the scheme defaulting to `https` if not specified."],["The document also lists various available versions of the `ProxyConfig` class, from version 2.10.1 up to the latest release candidate 2.37.0-rc."],["The `ProxyConfig` class is made up of modifiers, such as `set_hostname`, `set_port`, `set_username`, `set_password` and `set_scheme`, along with returning modifiers like `hostname`, `port`, `username`, `password` and `scheme`."]]],[]]
