Skip to content
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

[Feature]: calculate Network Size #142

Open
1 task done
rentalhost opened this issue Dec 27, 2023 · 0 comments
Open
1 task done

[Feature]: calculate Network Size #142

rentalhost opened this issue Dec 27, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@rentalhost
Copy link

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?

1. Launch app;
2. GET https://registry.npmjs.org/node-fetch
3. 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!

image

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
@rentalhost rentalhost added the bug Something isn't working label Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant