-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Proposal v4.0 b1 (HTTP/2+3, OS Trust Store, Custom DNS, OCSP, ...) #1531
base: master
Are you sure you want to change the base?
Conversation
46f030c
to
16ccc1b
Compare
16ccc1b
to
741017e
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
faf9aef
to
c12f000
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #1531 +/- ##
==========================================
- Coverage 97.28% 0 -97.29%
==========================================
Files 67 0 -67
Lines 4235 0 -4235
==========================================
- Hits 4120 0 -4120
+ Misses 115 0 -115 ☔ View full report in Codecov by Sentry. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
52653e4
to
247b382
Compare
0b4eebb
to
7dd1152
Compare
So far, I identified this: |
We can add the following arguments and document them:
|
7dd1152
to
7257a74
Compare
I've added and documented it.
Ideally, the connection information (TLS, Cipher, Peer/Issuer Certificate, and OCSP) should be in the request metadata and with a lexer instruction. |
7257a74
to
4c246e4
Compare
4c246e4
to
f034379
Compare
Damn this looks so tantalizing. I'd love for this to get packaged as a tryout / beta. Something installable via e.g. |
f034379
to
df42bba
Compare
Looks like it could be a big step forward if @jkbrzt approves it. Last week I wanted to test resolving over IPv4 vs IPv6. I found that the released version could not help with this task, but it worked perfectly in the fork, with the same |
non https server were expected to receive "secure" cookies...? this seems to be a bug that lied in Requests for quite some time.
dec765c
to
d9db5a2
Compare
Excited to see HTTP/2 and HTTP/3 soon landing in HTTPie 🎉
I was wondering if we could have an equivalent to cURL's http-version flags i.e |
Likewise!
I first need to add a feature into Niquests, which isn't top priority right now. regards, |
94c960e
to
7cd6579
Compare
7cd6579
to
e3cbc7f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs typos:
Co-authored-by: Jan Brasna <1784648+janbrasna@users.noreply.github.com>
Co-authored-by: Jan Brasna <1784648+janbrasna@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of questions regarding how to surface some of the functionality and constraints to the users:
@@ -570,9 +570,10 @@ installation (only the supported ones are shown here). | |||
|
|||
|
|||
A string in the OpenSSL cipher list format. | |||
tls1.3 ciphers are always present regardless of your cipher list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may need a bit more context or outsider-friendly rewording. WDYT?
tls1.3 ciphers are always present regardless of your cipher list. | |
Applies only for TLS v1.2 and lower. TLS v1.3 connections always use the appropriate cipher suites available for that protocol version, regardless of this setting. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see https://docs.python.org/3/library/ssl.html#ssl.SSLContext.set_ciphers
we can't do anything about it. unless we're using http3 over quic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shortstory: Python hardcode it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not challenging anything from that. Most APIs are only handling tls12 ciphers, and don't bother with lower-level ctxs to set tls13 suites, esp. in OpenSSL world. — I'm only raising the need to explain that to consumers not familiar with the distinction in the new protocol RFC.
This PR showcases how HTTPie could evolve outside of Requests.
Niquests is supposed to be a (mostly) compatible fork of Requests.
Try this preview:
$ pip install "git+https://github.com/Ousret/HTTPie.git@feature-tryout-niquests" -U
Here are the biggest pros of this:
Obviously, cons:
Complete list of changes in the fork: https://github.com/jawah/niquests/blob/main/HISTORY.md
http
#1527--download
reports an "incomplete download" with Content-Encoding: gzip and content-length. #4234.0.0.b1 (unreleased)
User-Agent
, andAccept-Encoding
headers. (#1502)--resolver
. DNS over HTTPS, DNS over TLS, DNS over QUIC, and DNS over UDP are accepted. (#99) (#1531)--interface
. (#1422) (#1531)--local-port
. (#1456) (#1531)-6
or-4
. (#94) (#1531)requests_toolbelt
in favor of directly includingMultipartEncoder
into HTTPie due to its direct dependency to requests. (#1531)multidict
in favor of implementing an internal one due to often missing pre-built wheels. (#1522) (#1531)This fix has the particularity to consider 0 byte long stdin buffer as absent stdin. Empty stdin buffer will be ignored.
-1
to retrieve packets as they arrive. (#1531)From the HTTPie user perspective, they are "prettified" on the output by default. e.g. "x-hello-world" is displayed as "X-Hello-World".
.localhost
to the default loopback address. (#1458) (#1527)Existing plugins are expected to work without any changes. The only caveat would be that certain plugin explicitly require
requests
.Future contributions may be made in order to relax the constraints where applicable.