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

2020 Compression: request instead of response #1910

Closed
dtikhonov opened this issue Jan 22, 2021 · 1 comment · Fixed by #1911
Closed

2020 Compression: request instead of response #1910

dtikhonov opened this issue Jan 22, 2021 · 1 comment · Fixed by #1911
Labels
bug Something isn't working writing Related to wording and content

Comments

@dtikhonov
Copy link
Member

dtikhonov commented Jan 22, 2021

URL
https://almanac.httparchive.org/en/2020/compression#what-type-of-content-should-we-compress

Describe the issue
The use of the word "request" instead of "response" is inexact. Examples:

The figure shows the percent of requests of a certain content type using either Brotli [...]

and

[...] the percent of image requests that employ either Brotli [...]

Expected behavior
Certainly, it is the response that is compressed.

@dtikhonov dtikhonov added bug Something isn't working writing Related to wording and content labels Jan 22, 2021
@tunetheweb
Copy link
Member

Fair point. In HTTP Archive parlance it's measured in the requests table but yes it's still the response that is compressed. Fixed in #1911 along with a number of other edits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working writing Related to wording and content
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants