Bug: Content-Disposition Header Does Not Support UTF-8 Filenames

Suggestion Box Bugs
1

Hi Coda team,

I’ve encountered an issue that’s affecting international users and anyone working with non-ASCII filenames. When using the Content-Disposition header to serve downloadable files, Coda doesn’t appear to support the UTF-8 encoded filename fallback specified in the RFC 5987 format.

For example:

Content-Disposition: attachment; filename="resume.pdf"; filename*=UTF-8''r%C3%A9sum%C3%A9.pdf

This should prompt the user to download the file as résumé.pdf, but instead, Coda falls back to the ASCII resume.pdf version, ignoring the filename* parameter.

This causes problems especially when filenames need to preserve accents or non-English characters, which is important for localization and user experience.

Can you please confirm whether this is a known limitation or a bug? And if it’s the former, are there any plans to support proper UTF-8 handling in the Content-Disposition header?

Thanks for all the great work you do — I’d love to see Coda better support internationalization here!

1 Like