Redirecting error and the Protocol error.
Two error messages randomly pop-up while browsing or opening a new tab
The first messages show's this.. ```Firefox has detected that the server is redirecting the request for this address in a way that will never complete.``` And the other.. ```Firefox doesn’t know how to open this address, because one of the following protocols (mega) isn’t associated with any program or is not allowed in this context.```
Избрано решение
This issue can be caused by corrupted cookies or cookies that are blocked.
- check the permissions for the domain in the currently selected tab in "Tools -> Page Info -> Permissions"
- https://support.mozilla.org/kb/fix-login-issues-on-websites-require-passwords
Clear the cache and remove the cookies from websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).
"Clear the cache":
- Firefox/Options/Preferences -> Advanced -> Network -> Cached Web Content: "Clear Now"
"Remove the cookies" from websites that cause problems.
- Firefox/Options/Preferences -> Privacy -> "Use custom settings for history" -> Cookies: "Show Cookies"
See also:
- http://kb.mozillazine.org/The_page_is_not_redirecting_properly
- http://kb.mozillazine.org/Websites_report_cookies_are_disabled
Всички отговори (3)
Избрано решение
This issue can be caused by corrupted cookies or cookies that are blocked.
- check the permissions for the domain in the currently selected tab in "Tools -> Page Info -> Permissions"
- https://support.mozilla.org/kb/fix-login-issues-on-websites-require-passwords
Clear the cache and remove the cookies from websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).
"Clear the cache":
- Firefox/Options/Preferences -> Advanced -> Network -> Cached Web Content: "Clear Now"
"Remove the cookies" from websites that cause problems.
- Firefox/Options/Preferences -> Privacy -> "Use custom settings for history" -> Cookies: "Show Cookies"
See also:
Didn't solve the problem, I cleared all cookies and cache, but nothing changed. I'll reinstall Firefox and see if anything would change.
I refreshed Firefox and it seemed to fix the problem quite simply, Anyway Thank you very much for the fast reply and coming by.