> On 29.11.2024, at 10:09, Sassy Natan <sas...@gmail.com> wrote:
>
> Hi Group,
>
> I'm facing an issue with the way my log file is present with the new version.
> In the previous version the log file didn't include TAB or other special
> characters.
What was your previous version? The logfile sanitation is in place since 2019.
One can specify the behavior via the global parameter sanitizelogfiles.
The value of 0 means that no sanitize should happen.
The value 1 means that full sanitizing is in place, which means that
non-printable characters are written as hex values.
The sanitize value of 2 means that sanitizing happens in a human friendly
fashion: newlines are preserved, but sanitizing makes sure that multiline
content cannot not confused with different log file entries. After a new-line
character a continuation character starts the new line followed by 4 spaces.
The reason for printing hex representation for non-printable characters into
the log file were security audits, there exist several nasty attacks (but
probably not with the tab character).
An easy strategy without changing the logic in NaviServer is to remove tabs
from the source, or using a postprocessing filter (a sed one-liner).
-g
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
