Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

back button doesn't work in https google search

  • 2 (ردّان اثنان)
  • 5 have this problem
  • 1 view
  • آخر ردّ كتبه vijay750

more options

Google search seems to have made https mandatory when logged in. This breaks history and the behaviour of the back button from the results page back to the google search results page. I think that this is because google, upon clicking on a result link, redirects to the results page via an intermediary, obfuscated url, which causes the back button to also redirect back to the result page. This is exactly the same problem as described here: https://support.mozilla.org/en-US/questions/892406?e=es&as=aaq for which there is no solution, as google doesn't allow us to disable https anymore. BTW, this behaviour is not replicted on chrome, i.e., back button works correctly in spite of the intermediate redirecting page.

Google search seems to have made https mandatory when logged in. This breaks history and the behaviour of the back button from the results page back to the google search results page. I think that this is because google, upon clicking on a result link, redirects to the results page via an intermediary, obfuscated url, which causes the back button to also redirect back to the result page. This is exactly the same problem as described here: https://support.mozilla.org/en-US/questions/892406?e=es&as=aaq for which there is no solution, as google doesn't allow us to disable https anymore. BTW, this behaviour is not replicted on chrome, i.e., back button works correctly in spite of the intermediate redirecting page.

الحل المُختار

Hi,

You can try the NoScript add-on which may help.

Read this answer in context 👍 0

All Replies (2)

more options

الحل المُختار

Hi,

You can try the NoScript add-on which may help.

more options

Thank you! noscript seems to have fixed this spurious page in the history! Much appreciated.