Character outside of permitted range in Content Disposition

[bclozel]

There is a potential regression in the ContentDisposition header support. See #36328 (comment)

[bclozel]

After digging into this, I don't think this is strictly a regression. Before #36328, the filename parameter was encoded using the RFC 2047 mechanism. As noted in #36328, this parameter should not be encoded but instead should use ISO-8859-1. But as noted in RFC 6266 Appendix D:

Avoid using non-ASCII characters in the filename parameter. Although most existing implementations will decode them as
ISO-8859-1, some will apply heuristics to detect UTF-8, and thus might fail on certain names.

I guess this is what triggered the reported problem. Let's apply the recommendations here and use ASCII strictly for the filename parameter and try to transliterate characters when possible and use _ as a fallback.

[mikkosuonio]

Did this fix make it to version 7.0.8? I cannot find the commit from branch 7.0.x or tag 7.0.8.

[bclozel]

@mikkosuonio Indeed this was not applied to the 7.0.x branch, only main. I've updated this issue to reflected that. Are you seeing this problem in production right now?

[mikkosuonio]

Not problem in production. We just noticed this fix when developing a feature. We can wait and take this into use when it is released. Thank you for the fix and a quick response!