4 ms·
It is pretty standard practice to host assets on a "cookieless" domain you control, but not on the same domain as the original site. For example, www.example.co
by mixologic 11y ago
It is pretty standard practice to host assets on a "cookieless" domain you control, but not on the same domain as the original site. For example, www.example.com has all the html, but all of the images are hosted at www.images-example.com. That would skew the results considerably.
- lifeisstillgood 11y agoWhy use another domain and not a sub-domain? I assume something to do with the cookie-less comment - but not clear what?
- mixologic 11y agoThe main reason is sometimes you have *.domain.com authentication cookies for single sign in across a suite of sites, however you do not want those authentication cookies sent to domains that do not need authentication.