Document Overview

Timeline:

Architecture

In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described.

The main objective of this feature/product is: To improve page load time by performing overhead for connections (DNS lookup, TCP handshake, TLS handshake) before the connections are actually needed.

Design Documents: Link to any design or architectural documents here. (There are no design documents)

Components

The major component in this is the Seer, interface defined by nsINetworkSeer. This keeps track of URLs the user has visited, along with URLs that were loaded by the loading of the initial URL. For example, when the user visits http://example.com/index.html, we keep track of that, as well as the fact that visiting that URL also caused us to load , http://styles.example.com/style.css, and http://scripts.example.com/jquery.js because those resources were included in index.html. Then, the next time the user visits http://example.com/index.html, we can set up connections to images.example.com, styles.example.com, and scripts.example.com, reducing the overhead on the page load.

The seer does not record any data, nor does it take any action, when in private browsing mode.

Seer

The tables below simply summarize the data encountered by this component.

Stored Data:

Communication with Docshell

Communication with Script, Stylesheet, Font, and Image loaders

Communication with Firefox UI

User Data Risk Minimization

In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.

• none raised

Alignment with Privacy Operating Principles

In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.

See Also: Privacy/Roadmap_2011#Operating_Principles:

Principle: Transparency / No Surprises

• Only does pre-connect not prefetch
  • does not pre-connect to https addresses
• no data is actually sent to the site until a user actively clicks a link
  • DNS prefetch and TCP preconnect (which includes SSL handshake)
• honors settings in Private Browsing to erase data

Recommendations: (what can be improved)

• None

Principle: Real Choice

• users can disable the feature via about:config if they so choose
  • network.seer.enabled

Recommendations:

• None

Principle: Sensible Defaults

• defaults discussed above and are sensibly chosen

Recommendations:

• None

Principle: Limited Data

• no data is collected that is outside normal browsing already and Private Browsing is respected

Recommendations:

• None

Follow-up Tasks and tracking