Support for logging is abysmal, and documentation is missing

Attempting to change logging for requests is very complicated, can only be done application-wide (I think), and the documentation is missing.

Google finds many incorrect suggestions (mainly pointing to readthedocs documentation of requests version 0.x), the only workable information I found was at this stack overflow thread: https://stackoverflow.com/questions/10588644/how-can-i-see-the-entire-http-request-thats-being-sent-by-my-python-application

As a first step it would be good if the information from this thread (insofar as it is still correct) was included in the documentation somewhere.

But it would be a lot nicer if there was easier support for logging, possibly through a toolbelt module or something. Controlling logging on a fine-grained scale is vital, especially when you are trying to debug things like SSL-related errors (which are rather unintelligible in their own right) in a large scale application.

I understand that part of the problem is with urllib3, but I guess I have to start somewhere.

And I'm willing to help, if personpower is an issue.

Start by reviewing the linked Stack Overflow thread and the current Requests and urllib3 logging behavior. Determine which guidance remains correct and where the documentation should explain request logging, including its application-wide and fine-grained limits. Done means the supported logging workflow and relevant SSL-debugging considerations are documented accurately.