Comments on: Serving Static Content from a Cookieless Domain

By: Gray Ghost Visuals

Gray Ghost Visuals — Sun, 15 Jan 2012 02:01:05 +0000

I was looking around forever for a great explanation and I came to the right place. BAD ASS!!!!

Before your article my ySlow was 91 and after I setup a cookie-less sub-domain it jumped to 95! AWESOME!!!! Now I can eat all that fatty foods I want

I especially like that you included the examples for WordPress and Google Analytics.

Thanks for your smart and intelligent comments on this subject. I now have a cookie-less sub-domain and I think I like the option for organization purposes. However it gets tricky when your using WordPress because you’re flying through directories like Doc Brown.

By: Lilliane

Lilliane — Thu, 29 Dec 2011 19:31:25 +0000

Hi, I’m trying to diy optimize my website and found my way here. I followed the instruction and created a static.wanderlass.com cname

I’m not really techie so pardon me if this is a bit stupid. I don’t know how to do this.

“When you create the CNAME record you want to enter your static domain/subdomain as the “label”, “name”, or “alias” and your A record domain as the “content” or “value”. (The CNAME term, which stands for “Canonical Name”, actually refers to the domain you are mapping to, not the alias. The common practice of referring to the alias as the “CNAME” is in fact backwards.)”

Thanks,
Lilliane

By: Pablo

Pablo — Thu, 24 Nov 2011 03:46:22 +0000

Best written technical doc I’ve read on the net. Thanks for sharing!

By: Improving Page Speed

Improving Page Speed — Fri, 14 Oct 2011 15:11:01 +0000

[...] be sure to click on this RavelRumba.com link – how to prevent these sites from setting cookies on your CDN or static subdomain. You have to do a little more work – change some of your a href links, configure your Google [...]

By: Rob Flaherty

Rob Flaherty — Thu, 22 Sep 2011 13:31:13 +0000

Todd,
To serve cookieless assets from cdn.gaijinfarmer.com you would need to make your canonical domain http://www.gaijinfarmer.com. You could then set your cookies against the www subdomain only, keeping cdn and other subdomains cookie-free.

You don’t actually have to move any of your files… you just have to change the request URL so it points to your cookieless domain.