Doesn't allow passing a contextFactory to Agent.

[dreid]

This means that there is no way for a user to make treq do any certificate verification.

[mriehl]

Any update on this? We just had to drop treq in favor of raw twisted agent using code because of this.

[dreid]

@mriehl in the latest release you can construct an HTTPClient with a base IAgent. However that isn't exposed in the module level methods (I think those are going to go away, they just encourage you to write less testable code for pretty minimal gain).

Also worth noting that with twisted 14.0 and service_identity twisted does all the certificate validation by default, limiting the times when you need to explicitly pass a context factory.

[dreid]

HTTPClient is not currently documented but it should be (after it's given a better name) and I don't expect to break it in a backwards incompatible way.

[mriehl]

Thanks for the info! I'll have a look at the HTTPClient (our internal certificates are not really valid of course, so browser-style validation doesn't help, sadly).

[ldanielburr]

#80 allows for the passing of an IPolicyForHTTPS implementer to the treq top-level api, which serves the need described here.

[zgoda]

If I understand correctly, this would be the only one way to implement client certificate authentication.

[twm]

As this capability is present, I am closing this in favor of #269 (documenting how to use this to customize TLS).