Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

zstd not recognized as compression (new in M123) #15882

Closed
2 tasks done
selfisekai opened this issue Mar 23, 2024 · 0 comments · Fixed by #15883
Closed
2 tasks done

zstd not recognized as compression (new in M123) #15882

selfisekai opened this issue Mar 23, 2024 · 0 comments · Fixed by #15883
Assignees

Comments

@selfisekai
Copy link
Contributor

FAQ

URL

https://liberda.nl/weblog/trust-no-client/

What happened?

"Enable text compression" diagnostic appeared for the document

Enable text compression: Potential savings of 21 KiB. Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.

What did you expect?

recognizing zstd as a compression algorithm (it has shipped in M123)

What have you tried?

checked logs (reduced for clarity):

{
  "method": "Network.responseReceived",
  "params": {
    "type": "Document",
    "response": {
      "url": "https://liberda.nl/weblog/trust-no-client/",
      "status": 200,
      "statusText": "",
      "headers": {
        "content-encoding": "zstd",
        "content-length": "8155",
        "content-type": "text/html",
        "vary": "Accept-Encoding"
      },
      "responseTime": 1711224797711.976,
      "protocol": "h2",
    },
  }
}

How were you running Lighthouse?

CLI

Lighthouse Version

b64619a

Chrome Version

123.0.6312.58

Node Version

v21.7.1

OS

Alpine Linux

Relevant log output

No response

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants