Avatar for Username

Search Support

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.

Learn More

Echekwara usoro a. Biko jụọ ajụjụ ọhụrụ ma ọ bụrụ na ị chọrọ enyemaka.

Improper handling of RFC5987 HTTP parameters such as filename

  • 1 nzaghachinzaghachi
  • 1 nwere nsogbu anwere nsogbu a
  • 1 view
  • Nzaghachi ikpeazụ nke 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).

Asịsa ahọpụtara

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

Gụọ azịza a na nghọta 👍 0

All Replies (1)

pfriend
pfriend Jụọ onye nwe ya ajụjụ
more options

Asịsa Ahọpụtara

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

Edeziri site na pfriend