Firefox 13 does not allow page redirects in CUPS!!!
I don't want to allow outside sites to redirect pages, but it's ridiculous to have to hit "Allow" every time when using CUPS!
FF needs either an exception list or a localhost exception.
As in: prevent for all but local site requests.
被采纳的解决方案
The setting in "Preferences > Advanced" 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.
- Firefox/Edit > Preferences > Advanced > General : Accessibility : [ ] "Warn me when web sites try to redirect or reload the page"
See also:
- http://kb.mozillazine.org/accessibility.blockautorefresh
- http://kb.mozillazine.org/Accessibility_features_of_Firefox
所有回复 (5)
选择的解决方案
The setting in "Preferences > Advanced" 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.
- Firefox/Edit > Preferences > Advanced > General : Accessibility : [ ] "Warn me when web sites try to redirect or reload the page"
See also:
Interesting. I don't see how it would benefit accessibility, but I understand that this is apparently the purpose.
So, you are saying that SINCE it has nothing to do with security (which seems really odd to me), I should just turn it off.
Hmmmmmmm.
Anyway, I DO appreciate your taking the time to respond and clarify.
I don't say that is has nothing to do with security.
Only some specific redirects trigger the notification, so it doesn't mean much as a security measure (a server redirect via a new location doesn't).
It is implemented as an accessibility feature to avoid people from getting confused if they suddenly end up in another location without being aware of it.
Some servers use more than one redirect and in such a case you may have to click the allow button quite a few times.
Yes, I understood your answer, cor-el.
However, we now have something that MAY have something to do with security but is TARGETING accessibility issues.
AND for my problem the only solution is to turn it off altogether.
By the way, do you use Linux?