#http optimizations

[deltamumblings-blog]

HTTP Optimizations

HTTP 1.0 required strict "single request per connection" model, HTTP 1.1 reversed this behavior: by default, an HTTP 1.1 client and server keep the connection open, unless the client indicates otherwise (via Connection: close header).

Some key aspects to ensure:

Connection reuse: Ensure that your connection is not closed at end of each request, check header "Connection close"

Pipelining: Pipelining allows us to break the strict "send a request, wait for response" model. Instead, we can dispatch multiple requests, in parallel, over the same connection, without waiting for a response in serial fashion.

More details on browser implementations, http://en.wikipedia.org/wiki/HTTP_pipelining

IE 8 doesnt support Pipelining

Mozilla does, but is disabled by default

Chrome supports for HTTP but not for HTTPS

[myhippocampus-blog]

HTTP Optimizations

HTTP 1.0 required strict "single request per connection" model, HTTP 1.1 reversed this behavior: by default, an HTTP 1.1 client and server keep the connection open, unless the client indicates otherwise (via Connection: close header).

Some key aspects to ensure:

Connection reuse: Ensure that your connection is not closed at end of each request, check header "Connection close"

Pipelining: Pipelining allows us to break the strict "send a request, wait for response" model. Instead, we can dispatch multiple requests, in parallel, over the same connection, without waiting for a response in serial fashion.

http://www.igvita.com/2011/10/04/optimizing-http-keep-alive-and-pipelining/