4 ms·
Yes, 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 stat
by jasonkester 16y ago
Yes, 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.