-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
httplib debuglevel on CONNECT doesn't print response headers #57337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
httplib with a debuglevel prints out the response headers, but does not do so with CONNECT requests (when set_tunnel is used). Attached is a small patch to print the reply when the CONNECT request returns something other than 200 OK. I'm not sure if it is worth printing the headers when a 200 OK is given. If it seems useful I can update the patch. Thanks!!! |
The httplib module has been renamed to http.client in Python 3, besides which the attached patch isn't in the standard format that is used here. |
Attached a simple fix to the problem as written, matching logging method of HTTPResponse.begin(). |
Just happened to come across this now. Updated patch with test. |
Ping. |
Thanks for the patch! Could you revert unrelated changes (whitespaces, PEP-8 etc.) if you have time? |
Sure, I should have some time later today to do so. Should such changes not be made as they're encountered in order to clean On 2015-01-27 2:58 PM, Berker Peksag wrote:
|
New patch removes unrelated changes. |
New changeset dfbd07cdc031 by Berker Peksag in branch 'default': |
Thanks for the patch, Demian. I've simplified the test code a bit and committed it. Also, thanks for the report and for the initial patch Matt. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: