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.

Bug 1822453

Summary: Tomcat parses a request having an absolute URI path incorrectly and returns 404 Not Found after BZ#1455483
Product: Red Hat Enterprise Linux 7 Reporter: Masafumi Miura <mmiura>
Component: tomcatAssignee: Coty Sutherland <csutherl>
Status: CLOSED ERRATA QA Contact: tomcat-qe
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.8CC: cww, mmadzin
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-29 20:31:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1810269    
Attachments:
Description Flags
BZ1822453_proposed_patch.diff none

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