-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.5.3.1 preparation #818
2.5.3.1 preparation #818
Conversation
… deprecation and the GitHub Security Advisory.
It referenced an obsolete ESAPI property that was renamed to 'Validator.HtmlValidationAction'.
@xeno6696 - This should be really fast to review. The code changes are minimal (limited to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No changes requested, logging statement with the URL looks good. I'll comb through the documentation tweaks looking for typos and whatnot but that's not worth holding up a release.
@@ -382,6 +386,12 @@ public Date getValidDate(String context, String input, DateFormat format, boolea | |||
*/ | |||
@Override | |||
public boolean isValidSafeHTML(String context, String input, int maxLength, boolean allowNull) { | |||
// Ensure a message about deprecation is logged once if this or the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, this is pretty much straight up/downvote.
ESAPI 2.5.3.1 is a minor point release that adds:
Validator.isValidSafeHTML
andValidationRule.getValid
methods.isValidSafeHTML
methods is invoked. The warning notes that the method is deprecated and provides a link to the GitHub Security Advisory.