Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

back button doesn't work in https google search

  • 2 respostas
  • 5 têm este problema
  • 12 visualizações
  • Última resposta de 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.

Solução escolhida

Hi,

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

Ler esta resposta 👍 0

Todas as respostas (2)

more options

Solução escolhida

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.