Вы просматриваете вопросы по теме:
Вы просматриваете вопросы с метками:

Firefox Add-ons Store returns HTTP 406 Not Acceptable on direct connections, but works through a proxy

Hello, I would like to report an issue with the Firefox Add-ons Store. Recently, I suddenly encountered an "HTTP 406 Not Acceptable" error when trying to access the Firef… (читать ещё)

Hello,

I would like to report an issue with the Firefox Add-ons Store.

Recently, I suddenly encountered an "HTTP 406 Not Acceptable" error when trying to access the Firefox Add-ons Store. The store is completely unusable for me right now.

Here are the specific details:

Issue description: I have tried accessing the store on every network available to me, including mobile data, my office wired network, and my home wired network. Unfortunately, I get the same 406 error on all of them.

Timeline and context: Everything was working perfectly fine last week. I was able to search for and install a Markdown add-on without any issues. However, starting this week, it suddenly started returning the 406 error.

Additional troubleshooting:

I am not using a VPN or proxy. However, if I enable a proxy, the Add-ons Store works normally.

There is no antivirus software or firewall blocking Firefox's network requests.

Other websites load normally. Even mozilla.org works fine, but addons.mozilla.org does not.

I have also tried changing to other DNS resolvers, but that did not help.

Could you please help me understand why this is happening and how I can resolve it?

Thank you!

Открытый 1 41

how to return http response status code directly on error page?

am experiencing the 'fresh new look' error pages, and am rather annoyed that the raw response code isn't displayed on the initial error page, and must click 'learn more..… (читать ещё)

am experiencing the 'fresh new look' error pages, and am rather annoyed that the raw response code isn't displayed on the initial error page, and must click 'learn more...' to reveal the underlying response code. how can i return the error code to the initial error page and avoid the unnecessary extra click to get at that info?

(ps. i can assure you that by obscuring this basic piece of info, it definitely isn't 'making it clearer what went wrong', despite what the 149.0 patch notes claim)

Открытый 3