Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Browser Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 861
    • Issues 861
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor BrowserTor Browser
  • Issues
  • #21657
Closed
Open
Issue created Mar 06, 2017 by Arthur Edelstein@arthuredelstein

Test to make sure we isolate or disable all speculative connects

There are a variety of "resource hint" features in Tor Browser that we want to make sure are isolated by first-party or disabled. These include

  link rel=preconnect
  link rel=prefetch
  link rel=prerender

and possibly more. We should test this for the ESR45 and ESR52 versions of Tor Browser, because isolation will have different mechanisms.

See https://w3c.github.io/resource-hints/

We should also look into "SpeculativeConnect" code in Firefox to make sure there aren't any other cases of non-first-party isolated connections.

Assignee
Assign to
Time tracking