Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus
Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.
Résolu Archivé

Improper handling of RFC5987 HTTP parameters such as filename

Firefox
pfriend a répondu il y a 14 ans
pfriend
pfriend

I have files on my website whose names are in UTF-8 and contain characters outside the ASCII set. I am setting the Content-Disposition header as an attachment with a filename* parameter encoded per RFC5987. The non-ascii characters are translated fine, but there appears to be a problem handling space encoding (%20). Per this RFC spaces in the filename are encoded as %20, but when I download the file these encoded space characters are being converted to + characters which is incorrect. This appears to be a bug in Firefox (Chrome as well I might add).

I have files on my website whose names are in UTF-8 and contain characters outside the ASCII set. I am setting the Content-Disposition header as an attachment with a filename* parameter encoded per RFC5987. The non-ascii characters are translated fine, but there appears to be a problem handling space encoding (%20). Per this RFC spaces in the filename are encoded as %20, but when I download the file these encoded space characters are being converted to + characters which is incorrect. This appears to be a bug in Firefox (Chrome as well I might add).

Toutes les réponses (1)

pfriend
pfriend Auteur de la question

Solution choisie

Ignore this one. Turns out there was a unicode conversion bug that was causing this, Firefox is all good. :-)

Modifié le par pfriend