An option to inject custom headers into the request.
In some cases it is necessary to inject a custom header into the request. For example, because the protocol has added new headers and the library has not been updated to support them, or because
[[["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-21 UTC."],[[["This webpage provides access to the documentation for the `CustomHeader` class across multiple versions, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["The `CustomHeader` class allows users to inject custom headers into requests, which is useful for scenarios such as supporting new protocol headers not yet included in the library."],["The documentation covers the available constructors for the `CustomHeader` class, which include a default constructor and one that takes a name and value for the custom header."],["The documentation also lists the `custom_header_name()` function that returns the name of the custom header as a constant string."]]],[]]
