搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

downloading mp3 files

  • 3 个回答
  • 3 人有此问题
  • 1 次查看
  • 最后回复者为 jeronimo17

more options

Firefox 102.0 (65 bit) on Ubuntu 20.04, for some reason has begun downloading mp3 files as mpga files (Google Chrome doesn't do this). This forces me to edit the extension as I download, since my mp3 player doesn't recognize the mpga extension. How can I fix this?

Firefox 102.0 (65 bit) on Ubuntu 20.04, for some reason has begun downloading mp3 files as mpga files (Google Chrome doesn't do this). This forces me to edit the extension as I download, since my mp3 player doesn't recognize the mpga extension. How can I fix this?

所有回复 (3)

more options

One possibility is that the server is sending a novel Content-Type with the download. But if it's a multi-site problem, it's probably a stored data problem: Firefox stores file handling actions as you browse, and it may have stored the .mpga extension from one download as the standard file extension for "audio/mpeg" files.

Download actions are stored in the handlers.json file in your profile. The JSON format is difficult to edit/clean, but as a blunt approach, you can rename the file to hide it from Firefox and Firefox will start a new one from scratch.

To try that:

Open your current Firefox settings (AKA Firefox profile) folder using either

  • "3-bar" menu button > Help > More Troubleshooting Information
  • (menu bar) Help > More Troubleshooting Information
  • type or paste about:support in the address bar and press Enter

In the first table on the page, find the Profile Folder row. Click the "Open Folder" or "Open Directory" button on that row to launch the folder in your system file browser.

Leaving that window open, switch back to Firefox and Exit/Quit, either:

  • "3-bar" menu button > Exit/Quit
  • (menu bar) File > Exit/Quit

Pause while Firefox finishes its cleanup, then:

Right-click handlers.json then Rename to something like handlersOLD.json

Start Firefox back up and try the download again.

If you lose too many useful actions in this process, you could replace the new handlers.json with the old file.

more options

You can possibly check the HTTP response headers for this request in the Network Monitor.

more options