-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Any multipart request with a boundary in the content type raises an exception #1663
Comments
Hi, I've got same issues with 1.2.5.RELEASE |
Reopening to apply to Camden branch 1.2.x |
Thanks a lot! |
Here's a workaround with Camden.SR5 and Spring Boot 1.5 https://gist.github.com/spencergibb/80a134b4738c78ca64e4d0c77214fcb6 |
Cherry picked to 1.2.x ee953be |
Posting via zuul doesnt work in case the Content-Type has a charset specified. Applied fix from spring-cloud/spring-cloud-netflix#1663 fixes #403
Posting via zuul doesnt work in case the Content-Type has a charset specified. Applied fix from spring-cloud/spring-cloud-netflix#1663 fixes codecentric#403
From the above message it seems that the fix is done for this. However ,we tried after upgrading the boot dependencies to 1.5.1.RELEASE & spring-cloud-dependencies to Camden.SR5, it still didn't work for us. With what versions the fix for "-MIME type may not contain reserved characters" is supposed to work |
It looks like this was cherry picked after the release occurred, can your try |
Thanks Ryan !! I will check with the SNAPSHOT version and let you know. Is the fix available in any DALSTON version as well? Is there any other to resolve this besides updating the dependency. I saw some messages regarding using the RibbonRoutingFilter instead of the SimpleHostRoutingFilter. |
Yes, it will be in Dalston RC1. The gist above is a workaround. |
So there is no other Camden Release lined up including the fix? |
There will be another Camden release coming soon. |
Hi @ryanjbaxter - how soon is soon going to be? :-)
|
@hartmut-pq most likely this week, sorry for the delay |
@ryanjbaxter We hit this issue today, and as a result, a multipart upload feature is busted. Do you have a definitive timeline for this to be released? I'd like to avoid upgrading to SNAPSHOT, if I can, only to upgrade to a release couple days later. |
Camden.SR6 will hopefully be released today, if not Monday I would think at the latest. The Netflix 1.2.6.RELEASE which will be included in Camden.SR6 is already in Maven Central if you would like to try it out. |
@ryanjbaxter Thanks for the info. Please provide an update here when the release is available and I'll go grab it. |
The release is now available. |
Confirmed working. Thanks @ryanjbaxter |
Posting via zuul doesnt work in case the Content-Type has a charset specified. Applied fix from spring-cloud/spring-cloud-netflix#1663 fixes #403
Posting via zuul doesnt work in case the Content-Type has a charset specified. Applied fix from spring-cloud/spring-cloud-netflix#1663 fixes #403
In 1.3.0.M1 seems that a bug has been introduced.
Any multipart request that in his
Content-Type
adds theboundary
parameter (in theory a required parameter, see RFC) raises an exception with the message "MIME type may not contain reserved characters".I think it has been introduced in the commit which tries to handle well a content-type with a charset due to the upgrade of the
httpclient
library.I will try to open a PR with a fix in order to have it for this release.
The text was updated successfully, but these errors were encountered: