RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When testing JBCS we discover that DeflateAlterETag directive is missing in rhel9,

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Add DeflateAlterETag AddSuffix in httpd.conf
2. start httpd

Actual results:

AH00526: Syntax error on line xxx of path/conf/httpd.conf:
Invalid command 'DeflateAlterETag', perhaps misspelled or defined by a module not included in the server configuration

Expected results:

DeflateAlterETag working as in JBCS previous version.

Additional info:

See https://issues.redhat.com/browse/JBCS-255

Note I ported https://github.com/apache/httpd/commit/0eb1b009f6c30f86d67d016216454311c54642e2 for JBCS-255 expecting it will make it to 2.4.x some day :-(

Is there a reason this is not suitable for 2.4.x upstream, or you mean you just didn't get round to submitting the backport proposal?

I have forgotten to submit the backport proposal :-(
I will do it now.