This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Encoder Comparison Reference Project"
| Line 73: | Line 73: | ||
* xxx | * xxx | ||
* xxx | * xxx | ||
| + | |||
| + | = What I did with this tool = | ||
| + | * At Blackboard, we used it to further train Developers on how each encoding method differs from the other. We used it to explain to Architects why the native framework encoding libraries were inadequate [[User:Stephanie_Tan|Stephanie Tan]] | ||
= Road Map and Getting Involved = | = Road Map and Getting Involved = | ||
Revision as of 05:36, 11 February 2014
OWASP Encoder Comparison Reference ProjectLibraries and frameworks encode ASCII characters differently. The OWASP Enterprise Security API (ESAPI) is the reference implementation for the most comprehensive and secure output encoding/escaping. Using this encoder comparison table, you will see how ESAPI exceeds other framework encoders and native encoders. The OWASP Encoder Comparison Reference Project is a web-based table reference for how ESAPI and other framework and native language encoding methods work against ASCII characters. Project LeaderLicensingOWASP Encoder Comparison Reference is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
|
 Quick Download
News and Events
Related Projects
|
