[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2020-01-07 Thread bugzilla
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

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2020-01-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-12-06 Thread bugzilla
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

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-12-02 Thread bugzilla
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 >

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-11-28 Thread bugzilla
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

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-11-27 Thread bugzilla
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

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-11-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 Michael Osipov changed: What|Removed |Added CC||micha...@apache.org -- You are

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-11-27 Thread bugzilla
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

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-11-27 Thread bugzilla
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,

[Bug 63966] Charset of TLS message is hardcoded to ISO-8859-1.

2019-11-27 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63966 Remy Maucherat changed: What|Removed |Added Severity|normal |enhancement -- You are receiving