[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 --- Comment #8 from madhavpulip...@gmail.com --- Thank you team, Please help with the same fix in tomcat-embed-core also and also let us know when 8.5.51 will be available from maven central. regards, Madhav Pulipaka -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Mark Thomas --- Fixed in: - master for 9.0.31 onwards - 8.5.x for 8.5.51 onwards Feature is not present in 7.0.x -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 --- Comment #6 from madhavpulip...@gmail.com --- Thanks for your response, Converting the message to UTF-8 is sufficient so that all messages to client will be in UTF-8. Please ignore my request on making it configurable. regards, Madhav Pulipaka -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 --- Comment #5 from Christopher Schultz --- (In reply to Mark Thomas from comment #4) > If you i18n the message that that needs to be driven by the user agent's > locale rather than the server locale which would make the whole process > significantly more complicated. I don't see that change being made for this > feature. > > I'm not against switching the hard-coded message to UTF-8 - that would be > consistent with Tomcat's use of UTF-8 elsewhere and would also be a slightly > shorter response. +1 > What I am against is making this encoding configurable without an acceptable > justification for adding that complexity. +1 -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 --- Comment #4 from Mark Thomas --- If you i18n the message that that needs to be driven by the user agent's locale rather than the server locale which would make the whole process significantly more complicated. I don't see that change being made for this feature. I'm not against switching the hard-coded message to UTF-8 - that would be consistent with Tomcat's use of UTF-8 elsewhere and would also be a slightly shorter response. What I am against is making this encoding configurable without an acceptable justification for adding that complexity. -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 --- Comment #3 from Christopher Schultz --- (In reply to Mark Thomas from comment #1) > The response is correctly signalled as ISO-8859-1 encoded and is spec > compliant. How long before we stuff the response text into a localized properties file and have to chance it to UTF-8 to make it work? Perhaps /we/ should bend rather than the bug reporter? -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 Michael Osipov changed: What|Removed |Added CC||micha...@apache.org -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 --- Comment #2 from Michael Osipov --- (In reply to Mark Thomas from comment #1) > I'm curious. What is the use case for this (other than wanting everything to > be UTF-8 for $reasons)? > > The response is correctly signalled as ISO-8859-1 encoded and is spec > compliant. > > To put it another way, I'm struggling to identify a scenario where this > would not work as intended so why spend time making this configurable? I share this opinion, one could of course turn into US-ASCII, but hat won't change anything here. -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 --- Comment #1 from Mark Thomas --- I'm curious. What is the use case for this (other than wanting everything to be UTF-8 for $reasons)? The response is correctly signalled as ISO-8859-1 encoded and is spec compliant. To put it another way, I'm struggling to identify a scenario where this would not work as intended so why spend time making this configurable? -- 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
[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 Remy Maucherat changed: What|Removed |Added Severity|normal |enhancement -- 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
