OpenLiberty / OpenLiberty/docs
Documentation unclear: compression
@seshadhri-aswath is already working on this.
Since Aug 18, 2025.
- Dominant language
- No language data
- Stars
- 14
- Forks
- 58
- Avg merge
- 4m
- Merged PRs (30d)
- 35
Description
Hi,
I have a few issues with the compression documentation.
It was outlined here: https://openliberty.io/blog/2020/04/22/http-response-compression.html
The actual docs I am referring to: https://openliberty.io/docs/latest/reference/config/compression.html
Here are some enhancements I would like to suggest:
Compression algorithm
currently, we have support for:
- gzip,
- x-gzip,
- deflate,
- zlib,
- identity
Update wish / recommendation
- Please explain each item (I thought deflate is the algorithm used in gz?).
- Mention identity equals no-compression
- Mention zlib is hardly supported by browsers
- Mention zlib has AIX hardware support (has it?)
Future perspective: brotli, lz4 and zstd
Modern browsers will send: Accept-Encoding: gzip, deflate, br, zstd (Firefox, Edge, others).
Please document the small overlap and maybe reference wishlist issues / github RFE issues for br (brotli) and zstd (and maybe lz4).
serverPreferredAlgorithm
This is an attribute, interestingly. Make that information stand out, maybe add an example. Usually server.xml uses tags only, so this is somewhat unexpected.
Luckily, <config onError="fail" /> will make the startup fail.
types
Invalid tags won't fail the start
<config onError="fail" /> will NOT make the startup fail if you accidentally use <type> instead of <types>.
Please mention this explicitly (and why it DOES fail for <serverPreferredAlgorithm>, see above section).
Give examples of configurations
Give an example snipped for the default configuration
combination of no prefix, + and -
What happens if you combine those?
<compression>
<types>text/plain</types>
<types>+text/*</types>
<types>-text/xml</types>
</compression>
What would be the outcome? What takes precedence? What about other combinations?
minGzipSize
This option is not documented
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.