OpenLiberty / OpenLiberty/docs

Configuring compression of HTTP responses

Open
#1,448 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
14
Forks
58
Avg merge
4m
Merged PRs (30d)
35

Description

Exact topics to be determined. Creating this issue as a placeholder so we don't lose it.

https://www.openliberty.io/blog/2020/04/22/http-response-compression.html

Plus:
=== Configuration pitfalls

If the HTTP transport encounters a configuration that is considered invalid, a warning message with an appropriate message is logged. If this happens, the link:https://www.openliberty.io/docs/ref/config/#compression.html[default value for the attribute] that was misconfigured is used.

The following message keys are associated to misconfigurations of the <compression> element's attributes: CWWKT0029W, CWWKT0030W, CWWKT0031W, CWWKT0032W, and CWWKT0033W. For more details of these messages, see the link:https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.messages.liberty.doc/com.ibm.ws.http.channel.internal.resources.httpchannelmessages.html[Liberty messages]. <-- This relates to us moving the Messages across to OL docs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Open Liberty blog post and the compression configuration reference. The issue is a placeholder, so first determine the exact documentation topics and how the CWWKT0029W–CWWKT0033W message information should move into Open Liberty docs. Done means the scope is resolved and the relevant compression configuration pitfalls and messages are documented.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.