Skip to content

#476 DefaultValidator.getValidInput uses canonicalize method argument - #477

Merged
kwwall merged 2 commits into
ESAPI:developfrom
jeremiahjstacey:Issue_476
Feb 2, 2019
Merged

kwwall merged 2 commits into
ESAPI:developfrom
jeremiahjstacey:Issue_476

Conversation

@jeremiahjstacey

Copy link
Copy Markdown
Collaborator

Implementation and test updates consistent with the recommended approach. StringValidationRule behavior for canonicalization is now configurable & DefaultValidator uses that configuration when evaluating a valid String input.

Tests updated to match expectations.

Exposing behavior in the StringValidationRule to allow an implementor to
opt-out of encoder canonicalization behavior.  Tests added to verify
intended behavior.

DefaultValidator getValidInput has been updated to use the existing
canonicalize argument to configure the StringValidationRule delegate for
canonicalization behavior before validating the input reference.  Tests
updated to validate configuration occurs in workflow.

Additional test updates in the DefaultValidatorInputStringAPITest to
remove unnecessary mock configuration expectations, and to verify that all
expected mock interactions have occurred.
Adding recommended logging if canonicalization is set to false.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants