Non-ISO8859-1 filenames creating garbled header in multipart request

[floydm4n]

Jersey depends on javaee/metro-mimepull to parse multipart request header (maybe not accurate but doesn't matter) and there is a long-standing unsolved bug (javaee/metro-mimepull#7) in it. So Jersey has the same problem, too.
It's a tiny problem and I provided a solution (javaee/metro-mimepull/pull/16), thought it could be fixed quickly. But one of the maintainers told me PRs are not going to be accepted at now for other reasons.
Overall, my idea is to add an option to let users configure header encoding, while the old behavior remains exactly the same if the option is not touched.
I create this issue to reference it so that Jersey may update mimepull version later and passing in the encoding option to get the right result. And I hope, if lucky enough, there are someone who has connections with both projects and can push the progress faster. This issue affects my production applications! Thanks in advance.