Encode non-printable character in Content-Disposition parameter #35034
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Milestone
The "filename" parameter value for the "Content-Disposition" header would contain non-printable characters, causing parsing issues for HTTP clients. We should ensure that all non-printable characters are encoded to avoid such issues.
The text was updated successfully, but these errors were encountered: