What steps will reproduce the problem?
1. Run JUnit tests with ESAPI
I just want to confirm that this is the intended behavior of this release.
There is Antisamy code commented out in the method.
Product version: ESAPI v1.1.1 Complete JAR file
Original issue reported on code.google.com by robert.m...@gmail.com on 7 Apr 2008 at 5:38
Original issue reported on code.google.com by
robert.m...@gmail.com
on 7 Apr 2008 at 5:38