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

Avatar for Username

Поиск в поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее
Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.
Решено Архивировано

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

Firefox Решение проблем
Chris Anderson отвечено
theconquistadork
theconquistadork

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

Все ответы (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor

Выбранное решение

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.

theconquistadork
theconquistadork Задавший вопрос

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