Closed snuggs closed 7 years ago
the diff implies that you have zopfli and brotli confused. i don't think you'd want to mix them together. zopfli is gzip compatible output but trading compress time for size savings. brotli is an entirely different, incompatible compression and has to be treated separately.
@brandondees testing gzip differences not brotli. Disabling brotli while testing. Will have both gzip and zopfli versions in for a bit while testing server payloads.
Hope this clears things up.
Jus testing.
gzip, zlib, deflate (respectfully)
.br
- brotli.gz
- gzip (via gzip library).gz2
- gzip (via zopfli library).zo
- zlib (via zopfli)Switching over to using zopfli
🏆 for gzip
compression.
@tmornini just a heads up! Says you recently updated here.
thanks for the clarification, all makes sense now.
Summary
Haven't found a sane gzip cli in node and don't really feel need a programing environment for this. Just a good command line script with decent args that I don't have to manually build and install. Zopfli covers both. Also determining using
gzip
(current manually installed library) vszopfli
libraries for GZIP compression (also testing ZLIB compression with Zopfli).Reason
README.md
will be super valuable for links.Satisfies Content Negotiation for
br
,gzip
,deflate
[Accept-Encoding
]() advertisements forContent-Encoding tokens
respectively for graceful degradation.https://en.wikipedia.org/wiki/HTTP_compression
Background Dependencies
Content-Encoding
negotiation) - https://github.com/koajs/staticResult
DEFLATE
d compression libraries. 💸gzip
versions on every run. (Now is idempotent).