Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jerseyrobot opened this issue Mar 16, 2018 · 2 comments
Open

Comments

@jerseyrobot
Copy link
Contributor

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.

@jerseyrobot
Copy link
Contributor Author

@andrepintorj
Copy link

This is a very important fix... Any luck when this will be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants