https://issues.apache.org/bugzilla/show_bug.cgi?id=52811
--- Comment #2 from hari <n.v.harikrishna.apa...@gmail.com> --- (In reply to comment #1) > That was fun. Lots of sneaky edge cases parsing that little lot. Ended up > implementing a new HTTP header parser. > > Fixed in trunk and 7.0.x and will be included in 7.0.27 onwards. > > I have proposed the fix for 6.0.x. I do have similar issue and tested with latest Tomcat 7 code. What I observed is: 1. When the content type is ending with 'start-info="text/xml;charset=UTF-8"', at the browser I am getting: 'start-info="text/xml;charset=UTF-8";charset=ISO-8859-1'. charset=ISO-8859-1 is appended to content type. 2. When the content type is ending with 'start-info="text/xml"; charset=UTF-8', at the browser I am getting the same thing. There is not problem with this case. My question is: In case 1: even though charset exist (which is mentioned as UTF-8) in content type string, I am getting another extra charset (which is ISO-8859-1). Is it the expected behavior? Does the given content type is considered to as invalid/unknown content type? -- 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
