Thanks for bringing this to our attention! It looks like the "workaround for yet another form of wrong Content-Disposition parameter encoding" (introduced in 6.0.8314) is triggering this error due to a bug. Apparently, the code is unable to handle some forms of wrongly-encoded MIME parameters. We will fix this for the next release. If you would like to get a hotfix in the meantime, please let me know.
↧