for in a message to identify the thread?
Check the message source for headers identifying the thread.
-Terence Bandoian
-Original Message-
From: Mark Thomas
Sent: Thursday, July 6, 2023 3:13 AM
To:users@tomcat.apache.org
Subject: Re: Can We Disable Chunked Encoding?
Please don't hijack threads
nal Message-
> From: Mark Thomas
> Sent: Thursday, July 6, 2023 3:13 AM
> To: users@tomcat.apache.org
> Subject: Re: Can We Disable Chunked Encoding?
>
> Please don't hijack threads by replying to a previous message and changing
> the subject. Start a new thread by sending a
Please don't hijack threads by replying to a previous message and
changing the subject. Start a new thread by sending a new message to the
list.
You also need to provide some version information.
Mark
On 06/07/2023 00:36, Eric Robinson wrote:
We've been seeing problems with failed requests
We've been seeing problems with failed requests where the response comes back
with duplicate chunked encoding headers:
[Response]
HTTP/1.1 200
Strict-Transport-Security: max-age=86400; includeSubDomains;
Cache-Control: no-cache,no-store
isAuthenticated: true
X-FRAME-OPTIONS: SAMEORIGIN
