GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||
GeezerVison is showing github.com — gh-66897: Upgrade HTTP CONNECT to protocol HTTP/1.1 by handlerbot · Pull Request #8305 · python/cpython Conversation
|
|
Working on fix for BytesWarning now. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks for updating that PR, I've just added this to my TODO list, but it may take a while. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Hi @berkerpeksag, circling back to this one, do you still have time and interest in the topic, or should we find another reviewer? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Is this going to be merged any time soon? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, I will try to review this PR this weekend. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
any update? this bug currently blocks any integretion with the linkerd2 proxy as this throws a 400 bad request for connections inititaded by python apps |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Can you show the exact error for this? «crash» usually describes a segfault of the interpreter, is that what happended or was it a regular Python exception? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Please answer: what exactly do you see when you say «it crashes»? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hi folks -- would love to try again to get this merged. :-) cc @berkerpeksag who I solicited the original review from, and tagging in @orsenthil and @SethMichaelLarson (I think this is the same GitHub identity for the person who approved #20959, that's who I am looking for, sorry if I tagged the wrong person) who have also reviewed PRs for |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sigh, I did mean @sethmlarson not @SethMichaelLarson, sorry about that, the GitHub autocompleter was determined to mislead me! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hi Michael, Thanks for following up. I will be able to review and bring it to a closure. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
any updates on this? would love to see this merge as it prevents our services from using certain proxies. thanks |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
why this PR is still open and not merged? and when can be merged? :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@handlerbot , @lukaszgalezewski - apologies. None of us go to it. I will review this in coming week and target for upcoming Python release (3.12, if features are allowed) otherwise we can go with 3.13. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@orsenthil do you have any update on this? Hope this can be merged in python 3.12. I recently run into this issue, even latest python can't set protocol version for HTTP CONNECT is kind of embarrassment. Thanks. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
It's not a feature, it's a shame. HTTP 1.0 is horribly obsolete, |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@vstinner @gpshead could you review and possible merge this PR please? (as committers into |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me.
I reviewed for the choices made for handling unicode, and sending Host with HTTP 1.1 for CONNECT, when not specified. And verified if it is backwards compatible.
The feedback in the comments seem to say this helps for folks who had a need too.
This change looks good to me.
Apologize for taking long time.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
* bpo-22708: Upgrade HTTP CONNECT to protocol HTTP/1.1 (GH-NNNN) Use protocol HTTP/1.1 when sending HTTP CONNECT tunnelling requests; generate Host: headers if one is not already provided (required by HTTP/1.1), convert IDN domains to punycode in HTTP CONNECT requests. * Refactor tests to pass under -bb (fix ByteWarnings); missed some lines >80. * Use consistent 'tunnelling' spelling in Lib/http/client.py * Lib/test/test_httplib: Remove remnant of obsoleted test. * Use dict.copy() not copy.copy() * fix version changed * Update Lib/http/client.py Co-authored-by: bgehman <[email protected]> * Switch to for/else: syntax, as suggested * Don't use for: else: * Sure, fine, w/e * Oops * 1nm to the left --------- Co-authored-by: Éric <[email protected]> Co-authored-by: bgehman <[email protected]> Co-authored-by: Oleg Iarygin <[email protected]>
* bpo-22708: Upgrade HTTP CONNECT to protocol HTTP/1.1 (GH-NNNN) Use protocol HTTP/1.1 when sending HTTP CONNECT tunnelling requests; generate Host: headers if one is not already provided (required by HTTP/1.1), convert IDN domains to punycode in HTTP CONNECT requests. * Refactor tests to pass under -bb (fix ByteWarnings); missed some lines >80. * Use consistent 'tunnelling' spelling in Lib/http/client.py * Lib/test/test_httplib: Remove remnant of obsoleted test. * Use dict.copy() not copy.copy() * fix version changed * Update Lib/http/client.py Co-authored-by: bgehman <[email protected]> * Switch to for/else: syntax, as suggested * Don't use for: else: * Sure, fine, w/e * Oops * 1nm to the left --------- Co-authored-by: Éric <[email protected]> Co-authored-by: bgehman <[email protected]> Co-authored-by: Oleg Iarygin <[email protected]>
|
@orsenthil Shall we also backport this to 3.11? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
No, this is more of a feature. it's a notable behavior change, not a mere unintended behavior fix. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.