Skip to main content
Webmasters

Return to Question

fixed grammar
Source Link
Clint Pachl
Clint Pachl
  • 180
  • 4

With plain HTTP, cookieless domains wereare an optimization to avoid unnecessarily sending cookie headers for page resources.

However, the SPDY protocol compresses HTTP headers and in some cases eliminates unnecessary headers. My question then is, does SPDY make cookieless domains irrelevant?

Furthermore, should the page source and all of its resources be hosted at the same domain in order to optimize a SPDY implementation?

With plain HTTP, cookieless domains were an optimization to avoid unnecessarily sending cookie headers for page resources.

However, the SPDY protocol compresses HTTP headers and in some cases eliminates unnecessary headers. My question then is, does SPDY make cookieless domains irrelevant?

Furthermore, should the page source and all of its resources be hosted at the same domain in order to optimize a SPDY implementation?

With plain HTTP, cookieless domains are an optimization to avoid unnecessarily sending cookie headers for page resources.

However, the SPDY protocol compresses HTTP headers and in some cases eliminates unnecessary headers. My question then is, does SPDY make cookieless domains irrelevant?

Furthermore, should the page source and all of its resources be hosted at the same domain in order to optimize a SPDY implementation?

Tweeted twitter.com/#!/StackWebmasters/status/278167671533629440
Source Link
Clint Pachl
Clint Pachl
  • 180
  • 4

Does the SPDY protocol eliminate the need for cookieless domains?

With plain HTTP, cookieless domains were an optimization to avoid unnecessarily sending cookie headers for page resources.

However, the SPDY protocol compresses HTTP headers and in some cases eliminates unnecessary headers. My question then is, does SPDY make cookieless domains irrelevant?

Furthermore, should the page source and all of its resources be hosted at the same domain in order to optimize a SPDY implementation?