8 ms·

Best answer so far. There is absolutely 0 legitimate reason (that i can think of anyway) a website should be making requests from your browser to another websit

• kazinator 5y ago
  It doesn't have to be Javascript. I made an application many years ago that used almost zero Javascript. The only piece of JS is an onLoad handler to position a cursor on a particular field when a page loads. The application uses its own web server, so the browser talks to localhost. For licensing, the application sends the user to my domain, whose pages can send the user back to the app on localhost, again with no JS. The NoScript suite detects and blocks that. The simple fact of a remote website serving up a local URL via dynamic HTML is enough.
  • netizen79865243 5y ago
    with "The application uses its own web server, so the browser talks to localhost." you are not actually saying that your application itself contains a webserver, running inside a browser, serving a website running on localhost, are you?
    • kazinator 5y ago
      In this case, the application is a native executable containing a web server. (It runs in the background, controlled by an icon in the desktop notification area, which can also be double-licked to open a browser to the application's URL).