JDK-8006530 : Base64.getMimeDecoder().decode() throws exception for non-base64 character after padding =
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2013-01-17
  • Updated: 2013-03-22
  • Resolved: 2013-02-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8 b77Fixed
Related Reports
Duplicate :  
JDK-8007379 - Base64.getMimeDecoder().decode() throws IAE for a non-base64 character after padding
Duplicate :  
JDK-8007433 - Base64.Decoder.decode(ByteBuffer, ByteBuffer) doesn't throw IAE for non-valid Base64 if writing could not be done
Relates :  
JDK-8007379 - Base64.getMimeDecoder().decode() throws IAE for a non-base64 character after padding
Description
(1) j.u.Base64.getMimeDecoder().decode() throws exception for non-base64 character after padding =. For example "AA==\n"
(2) j.u.Base64.getMimeDecoder().encoder() does not add line ending at the end of the result, this should be documented explicitly.