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-14 UTC."],[[["This document outlines the configuration for an HTTP Proxy, applicable to both REST and gRPC-based clients."],["The full URI format for the proxy is `{scheme}://{username}:{password}hostname}:{port}`, with `https` as the default scheme."],["The class `ProxyConfig` provides methods to set the `hostname`, `port`, `username`, `password`, and `scheme` for the proxy."],["The `hostname()`, `port()`, `username()`, `password()`, and `scheme()` functions allow for retrieval of the configured proxy settings."],["The document lists the available version history for the `ProxyConfig`, ranging from version 2.10.1 up to 2.37.0-rc, with links to the documentation for each version."]]],[]]
