https://bz.apache.org/bugzilla/show_bug.cgi?id=66392
--- Comment #1 from Han Li ---
(In reply to Michael Osipov from comment #0)
> May java.nio.charset.Charset.defaultCharset() would be better here, no?
No, I found the reason why not use java.nio.charset.Charset.defaultCharset() by
git commit log
https://bz.apache.org/bugzilla/show_bug.cgi?id=66370
--- Comment #9 from Isaac Rivera Rivas ---
Yes, if the default is changed and the property lookup is wrapped in a
privilege block it should fix at least the issues seen in Open Liberty. I've
tested with the changes in the proposed PR
https://gi
https://bz.apache.org/bugzilla/show_bug.cgi?id=66393
Michael Osipov changed:
What|Removed |Added
CC||micha...@apache.org
--
You are recei
https://bz.apache.org/bugzilla/show_bug.cgi?id=66393
Bug ID: 66393
Summary: ExtendedAccessLogValve's x-P(XXX) does not correspond
to the documentation
Product: Tomcat 8
Version: 8.5.84
Hardware: All
OS: All
https://bz.apache.org/bugzilla/show_bug.cgi?id=66392
Michael Osipov changed:
What|Removed |Added
CC||micha...@apache.org
--
You are recei
https://bz.apache.org/bugzilla/show_bug.cgi?id=66392
Bug ID: 66392
Summary: AccessLogValue's file encoding does not correspond to
the documentation
Product: Tomcat 8
Version: 8.5.84
Hardware: All
OS: All
https://bz.apache.org/bugzilla/show_bug.cgi?id=66370
--- Comment #8 from Mark Thomas ---
That is a fair point that the necessary privilege blocks should be in place
inside the EL.
If the default for the GET_CLASSLOADER_USE_PRIVILEGED system property was
changed, and the code that obtained the va
