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 "ESAPI-JavaStatus"
From OWASP
(→ESAPI 2.0 Release issues) |
|||
| Line 1: | Line 1: | ||
== ESAPI 2.0 Release issues == | == ESAPI 2.0 Release issues == | ||
| + | * Make sure, at least, that the Swingset docs state that the code is out of date until we get caught up to the 2.0 release. | ||
* Augment the Encoder | * Augment the Encoder | ||
** new naming convention | ** new naming convention | ||
Revision as of 22:46, 29 November 2009
ESAPI 2.0 Release issues
- Make sure, at least, that the Swingset docs state that the code is out of date until we get caught up to the 2.0 release.
- Augment the Encoder
- new naming convention
- new fine grained url encoding functions
- DOM XSS encoding functions
- Ensure all units tests run successfully for Windows+Linux via Java 1.5.0_22
- Split Swingset into 1.4 and 2.0 SwingSet
- Clean up Maven issues http://code.google.com/p/owasp-esapi-java/issues/detail?id=63
- Clean up issues around the validity of Safe File Upload classes and mechanism
- Other issues tracked via Google Code here
ESAPI 1.4 Release issues
- Upgrade 1.4 Maven configuration
- Fix Oracle encoder
