Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Improper handling of RFC5987 HTTP parameters such as filename

  • 1 răspuns
  • 1 are această problemă
  • 1 vizualizare
  • Ultimul răspuns de pfriend

pfriend
pfriend
more options

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).

Soluție aleasă

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

Citește acest răspuns în context 👍 0

Toate răspunsurile (1)

pfriend
pfriend Deținătorul întrebării
more options

Soluție aleasă

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

Modificat în de pfriend