Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

back button doesn't work in https google search

  • 2 Antworten
  • 5 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von 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.

Ausgewählte Lösung

Hi,

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

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (2)

more options

Ausgewählte Lösung

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.