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
Successfully decode invalid input #189
Comments
Thanks for the report; I'll look into it. |
This is related to #182. Since padding doesn't perform any useful function, the decode logic does not currently require it. I have some in-progress work to make padding required by default (but configurable to require no padding, or be indifferent). |
Give #198 a try and see if the error reporting works for your use case. |
Great, it works!
It failed when the invalid input " |
Released in 0.20.0. |
"djAuMC4x" is a valid base-64 encoded string whereas "djAuMC4" is not.
However, the latest v0.13.0 decodes both strings successfully when decoding the invalid one should fail.
The text was updated successfully, but these errors were encountered: