The new Amazon firefox extension prevents redirection.
This evidently happened a couple of days ago . My firefox, which is always up to date, suddenly stopped displaying many websites. The problem was the appearance of a fully BLANK page. After quite a bit of investigation, including a couple of uninstall/reinstall cycles, I realized that all the pages causing problems were trying to perform a redirection using a meta refresh tag. The info on the support site (here) said this was related to the browser configuration, but I had the configuration tag appropriately set false (the default value, which *allows* redirection). I actually tried setting it to true, and, curiously, when I did that I then got the browser message saying the redirection was blocked, and when I clicked on "allow" it went thru! To make a pretty long story a bit shorter, the problem turned out to be the OFFICIAL AMAZON FIREFOX EXTENSION--which was updated on Dec 10. When I removed that extension and restarted my firefox, everything started working properly again. I have notified Amazon of the problem, but I figured that it would be important to post this notice here, as well, since I presume other users are probably having the same problem.
If you are seeing this issue (and your "blockautorefresh" config parameter is properly set to false), click on the tools menu (upper right, horizontal bars), and choose "add-ons." On that screen, open the Extensions tab. If it shows the "official Amazon firefox extension" you need to remove that. It did not tell me to restart the browser at that point, but I did, just to be sure. That fixed the problem.
For the record, I'm running Windows 7, 64-bit OS, with service pack 1. And my firefox is up to date with version 42.0.
Modified by cor-el
Chosen solution
The rest of my comment isn't displaying properly for some reason, so here it is, without the newline that evidently caused the issue: If you are seeing this issue (and your "blockautorefresh" config parameter is properly set to false), click on the tools menu (upper right, horizontal bars), and choose "add-ons." On that screen, open the Extensions tab. If it shows the "official Amazon firefox extension" you need to remove that. It did not tell me to restart the browser at that point, but I did, just to be sure. That fixed the problem. For the record, I'm running Windows 7, 64-bit OS, with service pack 1. And my firefox is up to date with version 42.0.
Read this answer in context 👍 1All Replies (5)
Chosen Solution
The rest of my comment isn't displaying properly for some reason, so here it is, without the newline that evidently caused the issue: If you are seeing this issue (and your "blockautorefresh" config parameter is properly set to false), click on the tools menu (upper right, horizontal bars), and choose "add-ons." On that screen, open the Extensions tab. If it shows the "official Amazon firefox extension" you need to remove that. It did not tell me to restart the browser at that point, but I did, just to be sure. That fixed the problem. For the record, I'm running Windows 7, 64-bit OS, with service pack 1. And my firefox is up to date with version 42.0.
You accidentally had started that line with a leading space that I've removed. A leading space make Firefox format the line as a PRE tag.
I've marked your above reply as the solution to close this thread.
I have the problem but DO NOT have the " official Amazon firefox extention" So how do I check the " blockautorefresh" config???
See:
- Firefox > Options/Preferences > Advanced > General : Accessibility : [ ] "Warn me when web sites try to redirect or reload the page"
The setting in "Options > Advanced > General" is meant as an accessibility feature, as you can see by the label of that section, so that people with disabilities or people who use screen readers do not get confused and is not meant as a safety protection to stop redirecting.
See also:
Those instructions were fine, for the problem users evolved this into, but the problem I was talking about was SPECIFIC to the Amazon extension, and actually quite the reverse. The browser was NOT "warning" me about auto-refresh redirections, but rather was just showing a totally blank page when I set it to NOT warn. If I set the warning, then it behaved correctly, but if I told it *not* to warn me, that's where the extension was causing a total failure. So no, this reply does not solve the issue.