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:
https://git.centos.org/rpms/httpd/blob/0ac66abcd8d9406daa7ec6169971d2d8921d77fd/f/SOURCES/httpd-2.4.37-CVE-2022-29404.patch changes default LimitRequestBody from 0 (unlimited) to 1073741824 (1G). This, proposed as security fix, breaks valid use-cases (e.g. mod_dav where you really want to upload big files).

Version-Release number of selected component (if applicable):
2.4.37-54.module_el8.8.0+1256+e1598b50

How reproducible:
Always.

Steps to Reproduce:
1. Upgrade from previous release
2. Try to run your workload (in our case it is uploading big files >1G with mod_dav)

Actual results:
HTTP_REQUEST_ENTITY_TOO_LARGE (HTTP 413) is returned on requests that used to work before.

Expected results:
Either default stays or at least there is some bigger warning "THIS WILL BREAK YOUR SERVICE AFTER UPGRADE". Basically some better visibility to the fact that it will break stuff.

FTR, Upstream commit: https://github.com/apache/httpd/commit/92499e20034485c5e2d29cb85940e309573d976e

Hello Igor,

we were announcing this change in Release Notes[0] and you can also find info about it in Knowledge Base article[1].

Changing default value was part of the security fix.

[0] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.7_release_notes/new-features#enhancement_dynamic-programming-languages-web-and-database-servers
[1] https://access.redhat.com/articles/6975397

As Lubos says we were aware of the impact of this change and it was documented accordingly in the release notes.

Occasionally & regrettably we do need to make changes which can impact behaviour of existing deployments for security reasons.
Feel free to contact Red Hat Support if you need further assistance.