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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-02 UTC."],[[["This document outlines the `ProxyConfig` class, used to configure HTTP proxies for both REST and gRPC-based clients."],["The `ProxyConfig` class allows setting the hostname, port, username, password, and scheme for the proxy."],["The full URI for the proxy is constructed using the format `{scheme}://{username}:{password}@{hostname}:{port}`, with `https` as the default scheme."],["Modifiers like `set_hostname`, `set_port`, `set_username`, `set_password`, and `set_scheme` are available to configure the proxy settings, and each of them have a && and & version."],["You can access the configured proxy parameters through functions like `hostname()`, `port()`, `username()`, `password()`, and `scheme()`."]]],[]]
