Andrey Petrov

+100 to bringing the streaming encoder into urllib3.

(Related to #51, still would love to have this.)

There is a contrib module within urllib3 for ntlm auth: https://github.com/shazow/urllib3/blob/master/urllib3/contrib/ntlmpool.py Unfortunately it's somewhat messy, undocumented, and untested (thus why it lives in contrib). If this is something you're interested...

Cool. Reopen this issue if you want to discuss further. :)

@Anorov That would definitely be ideal. What kinds of changes would you require in urllib3 to allow for this?

@matt-hickford Sure. :) Consider yourself the owner of this lovely issue.

~~Generally our pattern has been to be explicit about fields which are immediately used in this layer, and implicit about fields which get passed further down. I feel this has...

Er I think I misread what you meant. Have you seen `RequestMethods.request_encode_url` and `RequestMethods.request_encode_body`? Are those what you're looking for?

Traditionally (when we would just deal with ConnectionPools and urlopen) I would say "lol just encode the url yourself!" but with our higher-level managers and RequestMethods, I think that's a...

PRs can be submitted for review whenever, we can schedule the merging when it makes sense. :)