net/http: add support for creating proxied TLS connections #39794
Labels
FeatureRequest
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
DialTLSContext
is documented as only being used for non-proxied requests.This is problematic because it means HTTPS CONNECT requests always use
crypto/tls
. This can violate business requirements and so on. (And can also lead to difficult to debug errors if you, uh, forget thatDialTLSContext
is only for non-proxied requests. Or if the proxy is added later.)Ideally,
Transport
would have aClient(net.Conn, ...) net.Conn
field that, if nil, would default tocrypto/tls
.The text was updated successfully, but these errors were encountered: