You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there! Right now, when we talk about Response Size, we're only looking at the uncompressed size. But, if we throw in something like Accept-Encoding: br (you know, for compression), we also want to take a peek at the Network Size, like ChromeNetwork tab does.
Steps to reproduce?
1. Launch app;
2. GET https://registry.npmjs.org/node-fetch3. Set `Accept-Encoding` to `br` (or `gzip`);
4. Send.
What did you expect to happen?
So, we might see a Response Size of 136KB, but in reality, it's only munching up about 44KB in Network Size because of compression. Just thought it'd be cool to show that compressed size in our Network Size metric for a clearer picture of what's really going on!
Platform
None
HTTPie Desktop version
2022.5.1
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What happened?
Hey there! Right now, when we talk about Response Size, we're only looking at the uncompressed size. But, if we throw in something like
Accept-Encoding: br
(you know, for compression), we also want to take a peek at the Network Size, like Chrome Network tab does.Steps to reproduce?
What did you expect to happen?
So, we might see a Response Size of
136KB
, but in reality, it's only munching up about44KB
in Network Size because of compression. Just thought it'd be cool to show that compressed size in our Network Size metric for a clearer picture of what's really going on!Platform
None
HTTPie Desktop version
2022.5.1
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: