You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two months ago similar issue has been submitted but has already been fixed and released so I'm opening a new one.
I also came across a server that is not robust enough and fails when charset is used as a parameter inside Content-Type header for multipart media type. As specified by RFC7578, only boundary is a required parameter and there are no optional parameters.
I'm submitting an issue for FormHttpMessageConverter. Same logic applied as a fix for #25885 can probably be used in this situation also.
Edit:
I know there is a workaround where one can use setMultipartCharset() to prevent charset from showing in header. In my opinion it would be better if Content-Type header was aligned with specification and it worked in same fashion as MultipartWriterSupport now works.
The text was updated successfully, but these errors were encountered:
Affects: 5.x
Two months ago similar issue has been submitted but has already been fixed and released so I'm opening a new one.
I also came across a server that is not robust enough and fails when
charset
is used as a parameter insideContent-Type
header formultipart
media type. As specified by RFC7578, onlyboundary
is a required parameter and there are no optional parameters.I'm submitting an issue for
FormHttpMessageConverter
. Same logic applied as a fix for #25885 can probably be used in this situation also.spring-framework/spring-web/src/main/java/org/springframework/http/converter/FormHttpMessageConverter.java
Line 478 in a109b4c
Edit:
I know there is a workaround where one can use
setMultipartCharset()
to preventcharset
from showing in header. In my opinion it would be better ifContent-Type
header was aligned with specification and it worked in same fashion asMultipartWriterSupport
now works.The text was updated successfully, but these errors were encountered: