Skip to content

Encode non-printable character in Content-Disposition parameter #35034

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

Closed
bclozel opened this issue Jun 12, 2025 · 0 comments
Closed

Encode non-printable character in Content-Disposition parameter #35034

bclozel opened this issue Jun 12, 2025 · 0 comments
Assignees
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

Comments

@bclozel
Copy link
Member

bclozel commented Jun 12, 2025

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.

@bclozel bclozel added this to the 6.2.8 milestone Jun 12, 2025
@bclozel bclozel self-assigned this Jun 12, 2025
@bclozel bclozel added in: web Issues in web modules (web, webmvc, webflux, websocket) type: bug A general bug for: backport-to-6.1.x Marks an issue as a candidate for backport to 6.1.x labels Jun 12, 2025
@github-actions github-actions bot added status: backported An issue that has been backported to maintenance branches and removed for: backport-to-6.1.x Marks an issue as a candidate for backport to 6.1.x labels Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant