base64::decode Not enough data to process padding

[Peter Heggie]

According to some posts on the internet, this error happens (usually) when the encoding of a document did not correctly add the necessary padding characters (=) to the end of the document to add up to the correct number of characters (that can then be decoded).

Has anyone seen this before? We use a third party vendor solution as a document repository and they send a copy of these documents to our Cloverleaf, encoded in base 64. About once or twice a month we get these errors. If this is encoded with software, shouldn’t it be  trivial amount of logic to ensure the correct number of padding characters are appended?

or is this a tcl error on my side that happens during decoding?

Thanks,

Peter

Peter Heggie
PeterHeggie@crouse.org

Topic

[Jim Kosloskey]

Peter,

Have you tried other base64 decoders on the same data?

There appear to be a number of them available.

I am thinking of using this as a sanity check. If a different decoder also fails then the source is at fault and I would challenge the vendor to prove their data can be successfully decoded.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Author]

Replies