https://bz.apache.org/bugzilla/show_bug.cgi?id=62912
--- Comment #9 from Franos <francois.courta...@gemalto.com> --- Hello, > Okay, so we have some clients that vitally depend upon the space being added > and other clients that vitally depend upon the space *not* being added. Why > should your clients win over the others? I think that in most cases the provider of a server side solution validates their developments with a fixed list of clients (eg list of User-Agent s). In such case we can control the response (HTTP header included) to be sent to those clients depending of the value read from the request in the User-Agent HTTP header. So why Tomcat is changing a value we have set at server side and we know it works with the list of User-Agent s we want to support ? More, in the tests I have performed, if the content sent to the client is character based, Tomcat appends automatically ";charset=ISO-8859-1", for example, with no space. So why sometimes, we have space and sometimes we haven't ? > The real question is "why is Tomcat bothering to re-format the content-type > header when it does not have to do so?". Yes, this is indeed the question I have. > I could see an argument for a "don't mutate content-type headers when no > charset is present", but that's not what you asked for. So consider I ask for that. Best Regards. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
