On 08/05/2023 22:04, Christopher Schultz wrote:
On 5/8/23 10:39, Mark Thomas wrote:
The port the client connects to is irrelevant. All that matters is the
host in the request line and the host header.
1. The host header MUST be present
2. If a host is present in the request line it MUST
Hi,
This makes sense now. Thank you for clarifying.
Best,
Alvaro
From: Christopher Schultz
Sent: Monday, May 8, 2023 5:04 PM
To: users@tomcat.apache.org
Subject: [EXTERNAL] Re: Question in regards to the Connector
allowHostHeaderMismatch when it is set to
Alvaro,
On 5/8/23 10:39, Mark Thomas wrote:
On 08/05/2023 13:52, Alvaro Garay wrote:
Hi Mark,
In the example above...the port remains the same (8143). How is it
different?
GET http://myhostname.company.com/api/v1/endpoint HTTP/1.1
The host is "myhostname.company.com"
Host:
On 08/05/2023 13:52, Alvaro Garay wrote:
Hi Mark,
In the example above...the port remains the same (8143). How is it different?
GET http://myhostname.company.com/api/v1/endpoint HTTP/1.1
The host is "myhostname.company.com"
Host: myhostname.company.com:8143
The host is
Hi Mark,
In the example above...the port remains the same (8143). How is it different?
From: Mark Thomas
Sent: Friday, May 5, 2023 4:56 PM
To: Tomcat Users List
Subject: [EXTERNAL] Re: Question in regards to the Connector
allowHostHeaderMismatch when it is set
5 May 2023 18:21:02 Alvaro Garay :
Hi,
Tomcat version: 9.0.73
Operating system: Unix z/OS System
I have a question in regard to the Connector attribute
allowHostHeaderMismatch=false which checks the request line is
consistent with the Host Header.
So in this scenario, I have the
Hi,
Tomcat version: 9.0.73
Operating system: Unix z/OS System
I have a question in regard to the Connector attribute
allowHostHeaderMismatch=false which checks the request line is consistent with
the Host Header.
So in this scenario, I have the request line using the absolute path with a
