Ok. I would say it is unlikely integrated compression is implemented in HTTP/2 as it was in the HTTP/1.1. We'll see, but it's probably a good idea to plan to migrate to a different solution for compression.
Right now, there's also no provision to pull configuration from the Connector as well, the UpgradeProtocol element is independent.

(In reply to Remy Maucherat from comment #4)
> Ok. I would say it is unlikely integrated compression is implemented in
> HTTP/2 as it was in the HTTP/1.1. We'll see, but it's probably a good idea
> to plan to migrate to a different solution for compression.
>
> Right now, there's also no provision to pull configuration from the
> Connector as well, the UpgradeProtocol element is independent.
Nginx can use gzip compression with http/2 module.
So I think, tomcat may also support.（sad...）
Maybe tomcat will support in the future...

Hi
I am trying to setup http2 with compression I agree this still does not work
Not sure what this previous comment means
Please do not reopen the report. Please post on the user list if you need further assistance.
It still broken so why should we not reopen this ticket

Hi
I am trying to setup http2 with compression I agree this still does not work
Not sure what this previous comment means
Please do not reopen the report. Please post on the user list if you need further assistance.
It still broken so why should we not reopen this ticket

This feature is not broken. It was implemented at the end of last year and has been confirmed to be working as intended on multiple occasions since then.
To expand on Remy's previous comment.
Do not re-open this report means exactly that. Do not re-open this report.
This report is the enhancement request to add compression support to HTTP/2. That support has been added so this issue has been resolved. That you can't get it to work does not mean that the feature is broken. Given that:
- there are no relevant code changes since the feature was added
- it has been confirmed working multiple times
the more likely explanation is a configuration issue, not a bug.
Looking at the configuration provided in comment #10, that report at least is clearly a configuration issue.
Configuration issues are support questions and Bugzilla is not a support forum. Hence re-opening a bug in order to obtain configuration help is not acceptable behaviour in this community.
The correct place to seek configuration assistance is the users mailing list. Hence the second part of Remy's comment.

This is ASF Bugzilla: the Apache Software Foundation bug system. In case
of problems with the functioning of ASF Bugzilla, please contact
bugzilla-admin@apache.org.
Please Note: this e-mail address is only for reporting problems
with ASF Bugzilla. Mail about any other subject will be silently
ignored.