FEATURE REQUEST - Provide custom request headers

[chrisdlangton]

Many endpoints are more commonly relying on a customer header to establish a TLS connection, without the header the connection will be dropped or 403 http code response sent.

I understand basicauth via Authorization header can already be added, this requested capability would do the same but not use a hard coded header name.

[drwetter]

How does that work? HTTP header comes in the TLS packet.

[pnieuwkamp]

I think Chris may not mean the actual establishment of the TLS connection, but the request that gets send after the connection is made. Some web services rely on a different header than the Authorization one to establish authorization. For instance, I have one that requires me to insert a HTTP header like: "ClientID: 0xDEADBEAF" otherwise it will not process the request.

[chrisdlangton]

correct, the response headers will not be sent without the correct/expected request headers

[drwetter]

ok, that's no big deal

[drwetter]

See PR merged above

[chrisdlangton]

Legend @drwetter this'll be a huge benefit for so many environments
Bash master @tosticated smashes another feature