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.
Bug 1822453 - Tomcat parses a request having an absolute URI path incorrectly and returns 404 Not Found after BZ#1455483
Summary: Tomcat parses a request having an absolute URI path incorrectly and returns 4...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tomcat
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Coty Sutherland
QA Contact: tomcat-qe
URL:
Whiteboard:
Depends On:
Blocks: 1810269
TreeView+ depends on / blocked
 
Reported: 2020-04-09 04:00 UTC by Masafumi Miura
Modified: 2023-12-15 17:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-29 20:31:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
BZ1822453_proposed_patch.diff (496 bytes, patch)
2020-04-09 04:07 UTC, Masafumi Miura
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4004 0 None None None 2020-09-29 20:32:01 UTC

Description Masafumi Miura 2020-04-09 04:00:32 UTC
Description of problem:
Tomcat fails to parse a request having an absolute URI path and returns 404 Not Found after BZ#1455483.

Version-Release number of selected component (if applicable):
tomcat-7.0.76-9.el7 onwards, which contains BZ#1455483

How reproducible:
Always

Steps to Reproduce:
Send a request having an absolute URI by using the telnet command like the following:
~~~
$ telnet 127.0.0.1 8080
...(snip)...
GET http://127.0.0.1:8080/ HTTP/1.1
Host: 127.0.0.1:8080
Connection: close

~~~

Actual results:
Tomcat returns "404 Not Found". Tomcat's access log contains the following log entry which indicates that tomcat treats the request path as "//127.0.0.1:8080/". But it should be "/".
~~~
127.0.0.1 - - [09/Apr/2020:12:28:21 +0900] "GET //127.0.0.1:8080/ HTTP/1.0" 404 983
~~~

Expected results:
Tomcat returns a response. Tomcat access log contains the following log entry which indicates that tomcat treats the request path as "/" correctly.
~~~
127.0.0.1 - - [09/Apr/2020:12:51:29 +0900] "GET / HTTP/1.1" 200 11217
~~~

Comment 13 errata-xmlrpc 2020-09-29 20:31:09 UTC
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 (Important: tomcat security and bug fix update), 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/RHSA-2020:4004


Note You need to log in before you can comment on or make changes to this bug.