My apologies. I wasn't aware that something else besides the subject line identifies a thread. I thought changing the subject line *IS* starting a new thread. Thanks for letting me know. For my own edification, what does the list look for in a message to identify the thread?
> -----Original Message----- > From: Mark Thomas <ma...@apache.org> > 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 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 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 > > Transfer-Encoding: chunked <<<<<<<<<<<<< > > X-XSS-Protection: 1; mode=block > > vary: accept-encoding > > Content-Encoding: gzip > > Content-Type: text/xml;charset=ISO-8859-1 > > Transfer-Encoding: chunked <<<<<<<<<<<<<< Duplicate > > Date: Wed, 05 Jul 2023 17:22:11 GMT > > > > This is a violation of RFC 7230, so our nginx proxy is dropping the request > and returning a 502 bad gateway error. I've spoken to F5 about this, and > there's no way to make nginx ignore this violation. Unfortunately, the app is > a > canned product, and we don't have access to the code. > > > > Is there a way to disable that behavior in Tomcat? > > > > -Eric > > > > > > Disclaimer : This email and any files transmitted with it are confidential > > and > intended solely for intended recipients. If you are not the named addressee > you should not disseminate, distribute, copy or alter this email. Any views or > opinions presented in this email are solely those of the author and might not > represent those of Physician Select Management. Warning: Although > Physician Select Management has taken reasonable precautions to ensure no > viruses are present in this email, the company cannot accept responsibility > for > any loss or damage arising from the use of this email or attachments. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
