Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Apache httpd does not log status code "413" in access_log when hitting LimitRequestBody. It logs status code "200" instead.
### Version-Release number of selected component (if applicable):
httpd-2.4.6-40.el7_2.4.x86_64
### How reproducible:
Anytime
### Steps to Reproduce:
1. Configure LimitRequestBody and mod_ext_filter:
LimitRequestBody 100
2. Prepare a test file which is larger than LimitRequestBody
dd if=/dev/zero of=/tmp/testfile bs=1 count=101
3. Sent a POST request with the file
curl -X POST -vs -T /tmp/testfile http://127.0.0.1/index.html
or
curl -X POST -vs -H "Transfer-Encoding: chunked" -F "test=@/tmp/testfile" http://127.0.0.1/index.html
### Actual results:
"413 Request Entity Too Large" was returned to the client (curl) and the following log messages were output in error_log:
~~~
[Fri Sep 02 21:05:03.488793 2016] [http:info] [pid 4790] [client 127.0.0.1:59214] AH01588: Requested content-length of 101 is larger than the configured limit of 100
[Fri Sep 02 21:05:20.864884 2016] [http:info] [pid 4791] [client 127.0.0.1:59216] AH01591: Read content length of 152 is larger than the configured limit of 100
~~~
But status code 413 was not logged but status code 200 was logged instead in access_log:
~~~
127.0.0.1 - - [02/Sep/2016:21:05:03 +0900] "POST /index.html HTTP/1.1" 200 339 "-" "curl/7.29.0" "Cookie: -" "Set-Cookie: -" 0 711
127.0.0.1 - - [02/Sep/2016:21:05:20 +0900] "POST /index.html HTTP/1.1" 200 339 "-" "curl/7.29.0" "Cookie: -" "Set-Cookie: -" 0 719
~~~
### Expected results:
status code 413 should be output in access_log.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2175
### Description of problem: Apache httpd does not log status code "413" in access_log when hitting LimitRequestBody. It logs status code "200" instead. ### Version-Release number of selected component (if applicable): httpd-2.4.6-40.el7_2.4.x86_64 ### How reproducible: Anytime ### Steps to Reproduce: 1. Configure LimitRequestBody and mod_ext_filter: LimitRequestBody 100 2. Prepare a test file which is larger than LimitRequestBody dd if=/dev/zero of=/tmp/testfile bs=1 count=101 3. Sent a POST request with the file curl -X POST -vs -T /tmp/testfile http://127.0.0.1/index.html or curl -X POST -vs -H "Transfer-Encoding: chunked" -F "test=@/tmp/testfile" http://127.0.0.1/index.html ### Actual results: "413 Request Entity Too Large" was returned to the client (curl) and the following log messages were output in error_log: ~~~ [Fri Sep 02 21:05:03.488793 2016] [http:info] [pid 4790] [client 127.0.0.1:59214] AH01588: Requested content-length of 101 is larger than the configured limit of 100 [Fri Sep 02 21:05:20.864884 2016] [http:info] [pid 4791] [client 127.0.0.1:59216] AH01591: Read content length of 152 is larger than the configured limit of 100 ~~~ But status code 413 was not logged but status code 200 was logged instead in access_log: ~~~ 127.0.0.1 - - [02/Sep/2016:21:05:03 +0900] "POST /index.html HTTP/1.1" 200 339 "-" "curl/7.29.0" "Cookie: -" "Set-Cookie: -" 0 711 127.0.0.1 - - [02/Sep/2016:21:05:20 +0900] "POST /index.html HTTP/1.1" 200 339 "-" "curl/7.29.0" "Cookie: -" "Set-Cookie: -" 0 719 ~~~ ### Expected results: status code 413 should be output in access_log.