Logs printed using println() are always printed and no option to disable them. about esapi-java-legacy HOT 2 CLOSED

You can set the optional system property -Dorg.owasp.esapi.logSpecial.discard=true as part of your JVM startup. Setting this value disables the output in question.

Source Code References
https://github.com/ESAPI/esapi-java-legacy/blob/develop/src/main/java/org/owasp/esapi/PropNames.java line 128
https://github.com/ESAPI/esapi-java-legacy/blob/develop/src/main/java/org/owasp/esapi/reference/DefaultSecurityConfiguration.java lines 269 - 281 and 884 - 903

from esapi-java-legacy.

Closed, as this as it is a duplicate of issue #500. You already can be disabled by setting the system property org.owasp.esapi.logSpecial.discard to 'true' before your application starts up; e.g.,

$ java -Dorg.owasp.esapi.logSpecial.discard=true ...

Unfortunately, it is important to leave this so that it defaults to 'false', otherwise the ESAPI team would spend way too much time answer questions about why ESAPI can't find its ESAPI.properties file. It is annoying once you get it working, but it is very helpful if you can't figure out why it is failing.

Admittedly, it's a bit obtuse as to where it's documented in the Javadoc. Apologies for that; we could to better. I've been meaning to add a FAQ to our GitHub wiki pages and add it there, and I have even considered adding something like:

To suppress these ESAPI start-up configuration messages, consider running as:
    java -Dorg.owasp.esapi.logSpecial.discard=true ...

but of course, to some, that would just add more needless noise and probably lots of people wouldn't notice it anyway.

Even though we're closing this, if someone thinks that ESAPI should emit a message similar to the hypothetical one mentioned above, feel free to create a new enhancement GitHub ticket.

from esapi-java-legacy.