Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

Filenames with encoded URLs no longer save correctly in URL Encode format as of 127.0

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 32 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย Chris Anderson

more options

Up to 126.0b9, files with encoded URLs in their filenames downloaded normally. As of 127 onward, however, it gets changed to _3A instead of %3A, etc. Is there a setting somewhere in config to revert this?

Example:

Supposed to be: test [sound=https%3A%2F%2Ffiles.catbox.moe%2Fe547nk.mp3].png Downloads as: test [sound=https_3A_2F_2Ffiles.catbox.moe_2Fe547nk.mp3].png

Up to 126.0b9, files with encoded URLs in their filenames downloaded normally. As of 127 onward, however, it gets changed to _3A instead of %3A, etc. Is there a setting somewhere in config to revert this? Example: Supposed to be: test [sound=https%3A%2F%2Ffiles.catbox.moe%2Fe547nk.mp3].png Downloads as: test [sound=https_3A_2F_2Ffiles.catbox.moe_2Fe547nk.mp3].png

วิธีแก้ปัญหาที่เลือก

It looks that things got changed and and valid separator characters are replaced by a space invalid separator characters are replaced by an underscore. There doesn't seem to be a way to affect this.

  • 1903881 - Incorrect filename encoding when downloading file from content servers.

Some changes are linking to a security bug (1891234, additional filename filter checks) that we can't inspect. See sanitizeFileName, line 3488.

อ่านคำตอบนี้ในบริบท 👍 0

การตอบกลับทั้งหมด (2)

more options

วิธีแก้ปัญหาที่เลือก

It looks that things got changed and and valid separator characters are replaced by a space invalid separator characters are replaced by an underscore. There doesn't seem to be a way to affect this.

  • 1903881 - Incorrect filename encoding when downloading file from content servers.

Some changes are linking to a security bug (1891234, additional filename filter checks) that we can't inspect. See sanitizeFileName, line 3488.

มีประโยชน์หรือไม่

more options

Ugh, that's unfortunate. I suppose I'll have to downgrade Firefox to fix this issue.

มีประโยชน์หรือไม่

ถามคำถาม

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.