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”.

Learn More

Why is firefox checking google's safe browsing API for some of our company's internal javascript files?

  • 1 resposta
  • 3 têm este problema
  • 6 visualizações
  • Última resposta de the-edmeister

more options

I work for an IT department on an internal web-based app. When firefox loads 2 specific js files, it sends a request to safebrowsing.clients.google.com. In our China offices, this request can take a long time to return, if at all, and firefox then blocks remaining content from the app server. I haven't checked the content of the js files, but is it possible that something like embedded URLs or other squirrely content of the js file is triggering firefox to phone google home?

I work for an IT department on an internal web-based app. When firefox loads 2 specific js files, it sends a request to safebrowsing.clients.google.com. In our China offices, this request can take a long time to return, if at all, and firefox then blocks remaining content from the app server. I haven't checked the content of the js files, but is it possible that something like embedded URLs or other squirrely content of the js file is triggering firefox to phone google home?

Todas as respostas (1)

more options

Firefox will check for an update to the SafeBrowsing file (urlclassifier3.sqlite and 2 associated files) that is stored in the Profile folder soon after Firefox is launched and then check periodically for as long as Firefox is open. To the best of my knowledge the SafeBrowsing API does not check with Google on a file by file basis, it uses the local file to check URL's.

Now, if your company configured their Firefox installations to not use the SafeBrowsing file to save HHD space with roaming profiles, Firefox might be checking externally - my guess.