Skip to content
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

Change action invoke to allow to set the charset #134

Merged
merged 1 commit into from
Sep 19, 2017

Conversation

thc202
Copy link
Member

@thc202 thc202 commented Sep 18, 2017

Change ZestActionInvoke to allow to set the charset used in read
operations, to ensure the script is loaded or the output of the program
read, always with expected charset (if not it would rely on the JVM
default charset, which is not always the same).
Update tests to check that the charset is de/serialised.

Related to zaproxy/zaproxy#3377 - ZAP can no longer load non UTF8
scripts

Change ZestActionInvoke to allow to set the charset used in read
operations, to ensure the script is loaded or the output of the program
read, always with expected charset (if not it would rely on the JVM
default charset, which is not always the same).
Update tests to check that the charset is de/serialised.

Related to zaproxy/zaproxy#3377 - ZAP can no longer load non UTF8
scripts
@psiinon psiinon merged commit ac02413 into zaproxy:develop Sep 19, 2017
@thc202 thc202 deleted the actioninvoke-read-utf8 branch September 19, 2017 09:17
@thc202 thc202 added this to the 0.14.0 milestone Jun 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants