-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
🤗 [Question]: More information about compression #2472
Comments
Thanks for opening your first issue here! 🎉 Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord |
I really want to join in on here since there are some unxecpected things I noticed:
I think the middleware compression is broken honestly/very bad structured. I ask myself, why precompressing is not working? compress (or static) is given the folder which it should serve files from, hence, it should precompress them all into At least thats how I think it should work. There also is a setting:
What does it do, when the accepted compression is br: 1-11 The question now is (for brotli) is BestCompression level 9 or level 11? In general there are a lot of settings missing I think. I would structure it like this: (defaults configured)
Note:
Many questions and the docs/manual does not provide much info. Also much potential to improve in functionality.
May I tag @ReneWerner87? Thanks :) |
Question Description
Is it possible to add more information about compression in the docs here?
Specifically, what are the minimum payload sizes for
gzip
,br
, anddeflate
in order for the compression to take place? Here it says forgzip
it is 1024KB, but it seems to be smaller fordeflate
What happens if multiple encodings are supplied in the header. It seems that the priorities look like this:
What if the header specifies multiple compression algos, but the one with the highest prio does require a higher minimum payload? Wouldn't it make sense to try to compress with another algo?
Code Snippet (optional)
No response
Checklist:
The text was updated successfully, but these errors were encountered: