Ads, Analytics and cookies...

Poul-Henning Kamp phk at
Sun Aug 17 09:21:43 CEST 2008

In message <08260D8D-FADF-40DB-8699-06900D960927 at>, =?ISO-8859-1?
Q?Ask_Bj=F8rn_Hansen?= writes:

>It doesn't really answer your question - but it usually makes sense to  
>serve the static content (css/js/images) from a completely different  
>domain.  For example at we use  
>to have a domain that's "cookie free" for static content.    Yahoo  
>uses "".
>You don't want the browsers to "upload" the cookies a gazillion times  
>to a server that doesn't even look at them anyway.   This also gives  
>you more flexibility to have your site served by one set of servers  
>and the static content served by another set of servers.

And just to be totally clear: you need different domains because that's
what cookies select on but you can serve the domains from the same
servers if you want.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

More information about the varnish-misc mailing list