Make it possible to track raw download size #127
Labels
enhancement
New feature or request
Comments
Ousret
added a commit
that referenced
this issue
Jun 24, 2024
**Added** - TransferProgress tracking in Response when downloading using `stream=True` based on the Content-Length. (#127) There's no easy way to track the "real" amount of bytes consumed using "iter_content" when the remote is sending a compressed body. This change makes it possible to track the amount of bytes consumed. The `Response` object now contain a property named `download_progress` that is either `None` or a `TransferProgress` object. - HTTP/2 with prior knowledge over TLS or via an unencrypted connection. `disable_http1` toggle is now available through your `Session` constructor. In consequence, you may leverage all HTTP/2 capabilities like multiplexing using a plain (e.g. non-TLS) socket. You may enable/disable any protocols per Session object (but not all of them at once!). In non-TLS connections, you have to keep one of HTTP/1.1 or HTTP/2 enabled. Otherwise, one of HTTP/1.1, HTTP/2 or HTTP/3. A `RuntimeError` may be thrown if no protocol can be used in a given context. **Changed** - Relax main API constraint in get, head, options and delete methods / functions by accepting kwargs. - urllib3-future lower bound version is raised to 2.8.900
Merged
Ousret
added a commit
that referenced
this issue
Jun 24, 2024
**Added** - TransferProgress tracking in Response when downloading using `stream=True` based on the Content-Length. (#127) There's no easy way to track the "real" amount of bytes consumed using "iter_content" when the remote is sending a compressed body. This change makes it possible to track the amount of bytes consumed. The `Response` object now contain a property named `download_progress` that is either `None` or a `TransferProgress` object. - HTTP/2 with prior knowledge over TLS or via an unencrypted connection. `disable_http1` toggle is now available through your `Session` constructor. In consequence, you may leverage all HTTP/2 capabilities like multiplexing using a plain (e.g. non-TLS) socket. You may enable/disable any protocols per Session object (but not all of them at once!). In non-TLS connections, you have to keep one of HTTP/1.1 or HTTP/2 enabled. Otherwise, one of HTTP/1.1, HTTP/2 or HTTP/3. A `RuntimeError` may be thrown if no protocol can be used in a given context. **Changed** - Relax main API constraint in get, head, options and delete methods / functions by accepting kwargs. - urllib3-future lower bound version is raised to 2.8.900
Ousret
added a commit
that referenced
this issue
Jun 24, 2024
**Added** - TransferProgress tracking in Response when downloading using `stream=True` based on the Content-Length. (#127) There's no easy way to track the "real" amount of bytes consumed using "iter_content" when the remote is sending a compressed body. This change makes it possible to track the amount of bytes consumed. The `Response` object now contain a property named `download_progress` that is either `None` or a `TransferProgress` object. - HTTP/2 with prior knowledge over TLS or via an unencrypted connection. `disable_http1` toggle is now available through your `Session` constructor. In consequence, you may leverage all HTTP/2 capabilities like multiplexing using a plain (e.g. non-TLS) socket. You may enable/disable any protocols per Session object (but not all of them at once!). In non-TLS connections, you have to keep one of HTTP/1.1 or HTTP/2 enabled. Otherwise, one of HTTP/1.1, HTTP/2 or HTTP/3. A `RuntimeError` may be thrown if no protocol can be used in a given context. **Changed** - Relax main API constraint in get, head, options and delete methods / functions by accepting kwargs. - urllib3-future lower bound version is raised to 2.8.900
|
As I promised. It is now possible to track the real download speed. see version 3.7 changes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When
Content-Encodingis applied, we only get access to the decoded data.HTTPie’s
--downloadfeature would benefit from having continuous access to a raw downloaded bytes counter so that it can provide a meaningful progress bar and validate that the downloaded size matchesContent-Length(httpie/cli#423, httpie/cli#1531).The text was updated successfully, but these errors were encountered: