3 ms·
Right, but how is this a problem that you can control? It's the client that sends back the cookies, not the server, and you can't control your clients. When you
by wyuenho 16y ago
Right, but how is this a problem that you can control? It's the client that sends back the cookies, not the server, and you can't control your clients. When you need to set a cookie, you just do.
I think this number needs some sort of clarifications from Steve Souders as to what he means.
- jasonkester 16y agoYes, this is a problem you can (and should) control. It's as simple as registering mysitecdn.com (assuming your main domain is mysite.com) and serving all static content from there. Never set cookies against your CDN domain and they will never be in your users browser, thus ensuring he won't send them back to you with every request.
- wyuenho 16y agoAh ha this makes more sense. So if I don't want to use a real CDN, I can just set my cookies with a domain www.mysite.com, serve all my static content from cdn.mysite.com and I'm all set?
- pistoriusp 16y ago100% correct. Just some clarification for those that don't get it. Setting cookies on mysite.com; means that the cookies will be pushed by the client for all subdomains for mysite.com (*.mysite.com); -- But if you're setting cookies from www.mysite.com you can serve media from cdn.mysite.com and the requests from cdn.mysite.com will not push cookies to your server.