629e18ad86
It was broken by CL 22378. The bug was in the situation when "==" (two padding chars) were at the end, the reading did not stop after the first '=', and thus one more char of output was generated. Add more unit-test for base64 decoding. |
||
---|---|---|
.. | ||
commons/io | ||
james/mime4j |