Message318752
I think something like “invalid length” message does make more sense in this case than the misleading “incorrect padding”.
It would also be great if there was a way to force it to try its best at decoding the string. :) |
|
Date |
User |
Action |
Args |
2018-06-05 13:07:28 | dniq | set | recipients:
+ dniq, mark.dickinson, taleinat, r.david.murray, serhiy.storchaka |
2018-06-05 13:07:28 | dniq | set | messageid: <1528204048.27.0.592728768989.issue33770@psf.upfronthosting.co.za> |
2018-06-05 13:07:28 | dniq | link | issue33770 messages |
2018-06-05 13:07:28 | dniq | create | |
|