From MozillaWiki
Jump to: navigation, search

tems to be reviewed: HTTP Pipelineing -

Introduce Feature

Goal of Feature, what is trying to be achieved (problem solved, use cases, etc)

  • HTTP 1.1 RFC-2616
    • reduce latency
  • attempting to roll this out in a robust and safe way that was not available in the past; make this more real world usable
  • we are remaining spec compliant
    • we attempt to detect if the other end is spec compliant or not and dealing with it
  • 2 problems that are known
    • server side, and dynamically black list (in memory and ability to store)
    • client-side proxies (e.g. anti-virus software) can break pipelining
      • We should look at how Chrome is handling these for its False Start implementation

What solutions/approaches were considered other than the proposed solution?

  • SPDY

Why was this solution chosen?

  • doing both (SPDY & pipelining)

Any security threats already considered in the design and why?

Threat Brainstorming

  • We cannot always detect when a connection has been corrupted (e.g. replies received out of order)
  • Server could interpret pipelined requests as one request
  • Re-requesting resources might cause side-effects (which aren't supposed to happen) multiple times
    • This has already been an issue due to our re-request for non-pipelined persistent conections; it is just more likely to happen now with pipelining.

Conclusions / Action Items

  • [bsmith] Private browsing mode: need to check that we don't save blacklist to disk when we are in private browsing mode
    • already covered according to Patrick