Hello Jonathan, There is a reference to a discussion on a Tomcat list regarding Tomcat roadmap at https://svn.apache.org/viewvc?view=revision&revision=1846691 If you open the file TOMCAT-NEXT.txt, you will see in it (section New items for 10.0.x onwards): "4. Clean-up content-type header processing. Remove the optional space after the ';' character (if any). Don't mutate the header if there is no charset parameter. See BZ 62912 for some discussion and additional references."
This is why I am worried because the fix is scheduled only, for the moment, for Tomcat 10 and neither for Tomcat 8.5.x (base for TomEE 7.1.x) nor for Tomcat 9.0.x (base for TomEE 8.0.0). Regarding the user-agent, it's ours and we don't have anything between Tomcat/TomEE and the client. Best Regards. -----Original Message----- From: Jonathan Gallimore [mailto:jonathan.gallim...@gmail.com] Sent: mercredi 21 novembre 2018 11:11 To: us...@tomee.apache.org Cc: dev@tomee.apache.org Subject: Re: Could you vote for this one please ? Thanks for sending this over. I've had a read through of the bug, and the response from the Tomcat team on the ticket. I note that there is reference to a discussion on a Tomcat list, but can't find a link to it (other than this one: https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftomcat.10.x6.nabble.com%2FBug-62912-New-Tomcat-adds-a-space-character-in-the-Content-Type-header-if-this-one-has-a-character-rr-td5080079.html&data=02%7C01%7CFrancois.COURTAULT%40gemalto.com%7C03da7170e1b540c5a7d708d64f99b50e%7C37d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636783918917597143&sdata=XCFQB7z84PfK9ioY%2BgA6fZi%2B4uAfxLw7GQUHwB6n9vs%3D&reserved=0, which seems to mirror the ticket). If you have one, it would be great if you can post it here so we can join the conversation. I'd suggest that providing a well-tested patch that includes a config setting to enable/disable the behaviour, in addition to voting on the issue would probably greatly increase the chances of success. Out of curiosity, what is the client/user-agent that is struggling with the issue, and do you have anything between Tomcat/TomEE (e.g. proxy server / load balancer) and the client? Jon On Wed, Nov 21, 2018 at 9:30 AM COURTAULT Francois < francois.courta...@gemalto.com> wrote: > Hello, > > We have an issue reported Bug 62912< > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz. > apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D62912&data=02%7C01%7CF > rancois.COURTAULT%40gemalto.com%7C03da7170e1b540c5a7d708d64f99b50e%7C3 > 7d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636783918917597143&sdata > =TtofsMNQilwenKQWglA7ZM661DdWjC1P7PQ8xYysJVg%3D&reserved=0> ( > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbz. > apache.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D62912&data=02%7C01%7CF > rancois.COURTAULT%40gemalto.com%7C03da7170e1b540c5a7d708d64f99b50e%7C3 > 7d0a9db7c464096bfe31add5b495d6d%7C1%7C0%7C636783918917597143&sdata > =TtofsMNQilwenKQWglA7ZM661DdWjC1P7PQ8xYysJVg%3D&reserved=0) > > Could you vote for it (to be included in the next Tomcat 8.5.x and > 9.0.x releases hoping those versions to be used by TomEE) ? > Thank you in advance. > > Best Regards. > ________________________________ > This message and any attachments are intended solely for the > addressees and may contain confidential information. Any unauthorized > use or disclosure, either whole or partial, is prohibited. > E-mails are susceptible to alteration. Our company shall not be liable > for the message if altered, changed or falsified. If you are not the > intended recipient of this message, please delete it and notify the sender. > Although all reasonable efforts have been made to keep this > transmission free from viruses, the sender will not be liable for > damages caused by a transmitted virus. > ________________________________ This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
