Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Caută ajutor

Atenție la excrocheriile de asistență. Noi nu îți vom cere niciodată să suni sau să trimiți vreun SMS la vreun număr de telefon sau să dai informații personale. Te rugăm să raportezi activitățile suspecte folosind opțiunea „Raportează un abuz”.

Află mai multe

back button doesn't work in https google search

  • 2 răspunsuri
  • 5 au această problemă
  • 92 de vizualizări
  • Ultimul răspuns dat de vijay750

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.

Soluție aleasă

Hi,

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

Citește răspunsul în context 👍 0

Toate răspunsurile (2)

Soluție aleasă

Hi,

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

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