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.2.15-54.el6_8.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 01 18:51:38 2016] [error] [client 127.0.0.1] Requested content-length of 101 is larger than the configured limit of 100
[Fri Sep 01 18:52:49 2016] [info] [client 127.0.0.1] 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 - - [01/Sep/2016:18:51:38 +0900] "POST /index.html HTTP/1.1" 200 415 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"
127.0.0.1 - - [01/Sep/2016:18:52:49 +0900] "POST /index.html HTTP/1.1" 200 415 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2"
~~~
### Expected results:
status code 413 should be output in access_log.
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com
### 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.2.15-54.el6_8.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 01 18:51:38 2016] [error] [client 127.0.0.1] Requested content-length of 101 is larger than the configured limit of 100 [Fri Sep 01 18:52:49 2016] [info] [client 127.0.0.1] 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 - - [01/Sep/2016:18:51:38 +0900] "POST /index.html HTTP/1.1" 200 415 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2" 127.0.0.1 - - [01/Sep/2016:18:52:49 +0900] "POST /index.html HTTP/1.1" 200 415 "-" "curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.19.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2" ~~~ ### Expected results: status code 413 should be output in access_log.