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-08-14 UTC."],[[["\u003cp\u003eThe latest version available for the \u003ccode\u003eCustomHeader\u003c/code\u003e class is 2.37.0-rc.\u003c/p\u003e\n"],["\u003cp\u003eThis webpage lists available versions of \u003ccode\u003eCustomHeader\u003c/code\u003e, ranging from the latest 2.37.0-rc down to version 2.11.0.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eCustomHeader\u003c/code\u003e class provides a way to inject custom headers into requests, useful when the protocol has new headers not yet supported by the library.\u003c/p\u003e\n"],["\u003cp\u003eThe class has two constructors, one default and one that accepts a name and a value as strings to setup the header, plus a function to read the header name.\u003c/p\u003e\n"]]],[],null,[]]
