[Bug 54177] jkmanager generates non-well-formed XML for certain server timezones

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54177

Rainer Jung <ra...@kippdata.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Rainer Jung <ra...@kippdata.de> ---
The time formatting is done usinf strftime(). That in turn uses LC_TIME (resp.
LC_ALL, LANG) to check the locale and charset to use. The Umlaut conmes form
the fact, that your system has a probably german locale set in one of those
variables. The fact that the umlaut is not UTF8 encoded as declared by the
jk-status XML header indicates, that you LC_TIME (or LC_ALL or LANG) points to
a 8859 de-Locale.

Unfortunately it is not safe to set LC_TIME in the jk status worker before
calling strftime(), because this would not be safe if the surrounding web
server runs in a multi-threaded way as is typical for today's use.

Instead of trying to guess the locale and transforming the characters fro that
locale to the UTF-8 charset, I have changed the formatting to use pure numeric
date strings in r1648352. Will be part of version 1.2.41.

As you said: non-ASCII data coming from configuration can and should be
avoided. If you find other places were the status worker produces
non-well-formed output, please let us know.

Thanks and regards,

Rainer

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org