On 11/01/2022 14:50, Joscha Cepok wrote
<snip/>
I didn't take a deeper look, why browsers add the timestamp to the
cookie header, so ignoring the timestamp and log it once seems fine for
me. But in case of multiple broken cookies, maybe all malformed content
of the header should be logged on INFO and not just once? I usually
don't like approaches, which distinguish between expected malformed
content and unexpected malformed content, but on the other hand, if
malformed content appears way too often it might be worth to have that
information.
I don't think there is a one size fits all solution which is why it is
configurable with a a reasonable default.
The error is logged via the UserDataHelper so system admins can choose from:
- all at debug
- first per day at info then debug for the rest
- all at info
- none
See https://tomcat.apache.org/tomcat-9.0-doc/config/systemprops.html for
full details.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
