network profile
| bio | website | donaldjenkins.com |
|---|---|---|
| location | Paris, France | |
| age | ||
| visits | member for | 1 year, 2 months |
| seen | Mar 14 '12 at 11:33 | |
| stats | profile views | 2 |
Donald (@donaldjenkins) mainly writes about tech trends, especially anything to do with Apple, blogging and the cloud. He also occasionally covers current affairs. Find out more
Elsewhere:
|
Mar 3 |
comment |
Google Analytics setting cookies on static content despite being on entirely separate domain Yeah, I use the html5boilerplate version of the GA code: it's really cool, loads in the end and still works… Oh well, never mind, I just like to understand things. |
|
Mar 3 |
comment |
Google Analytics setting cookies on static content despite being on entirely separate domain The only .js that sets cookies is GA, I've checked that in httpfox, which also shows that GA is setting a cookie on each of the static files I'm trying to keep separate. I also deliberately changed names and paths, so that the (old) cached versions would no longer be served. Here's a screenshot of the request and response headers for one of the image files: i.via.dj/EiOc to show you what I mean. The cookie is being requested despite the file being a new one... |
|
Mar 3 |
comment |
Google Analytics setting cookies on static content despite being on entirely separate domain Thanks for the comment. Yes they do, see the link I included in my first sentence. The Google Analytics code is set in the main domain. The static files are called in the main site but hosted in the separate static one. If GA can set cookies via a CNAME that defeats the purpose of separating them... |
|
Mar 3 |
revised |
Google Analytics setting cookies on static content despite being on entirely separate domain Clarified the fact that the culprit is Google Analytics |
|
Mar 3 |
revised |
Google Analytics setting cookies on static content despite being on entirely separate domain Clarified the fact that the culprit is Google Analytics |
|
Mar 3 |
revised |
Google Analytics setting cookies on static content despite being on entirely separate domain added 53 characters in body |
|
Mar 3 |
asked | Google Analytics setting cookies on static content despite being on entirely separate domain |
|
Mar 3 |
comment |
CDN CNAMEs not resolving to customer origin It's working—now that it's propagated—when set up as mentioned in my last comment, taking account of your suggestion, and moving the static content to cdn.dj. Thanks. |
|
Mar 3 |
awarded | Scholar |
|
Mar 3 |
accepted | CDN CNAMEs not resolving to customer origin |
|
Mar 3 |
comment |
CDN CNAMEs not resolving to customer origin Thanks for that suggestion. It occurred to me on reading your answer that I could achieve the same result more simply by storing the static content on cdn.dj, instead of donaldjenkins.info (since, as you correctly assumed, I wasn't planning to use the root domain of cdn.dj). That way I can free up donaldjenkins.info for another use, and keep the static content within the same domain. Then I added all the subdomains as customer origins with the relevant directory appended. Now we just need to see whether that works once it's propagated. |
|
Mar 3 |
awarded | Student |
|
Mar 2 |
revised |
CDN CNAMEs not resolving to customer origin edited body |
|
Mar 2 |
revised |
CDN CNAMEs not resolving to customer origin edited body |
|
Mar 2 |
revised |
CDN CNAMEs not resolving to customer origin deleted 5 characters in body |
|
Mar 2 |
comment |
CDN CNAMEs not resolving to customer origin Haha! I use via.djas my URL shortener: it's mapped to a bitly Pro account, also via a CNAME, and works out of the box without problems. |
|
Mar 2 |
comment |
CDN CNAMEs not resolving to customer origin Yeah, thanks. I send them an email linking to this post as it seemed easier to do that than explain over the phone, but haven't heard back yet. Thanks for responding—hope you understand why I really wanted cdn.dj for my cdn! |
|
Mar 2 |
revised |
CDN CNAMEs not resolving to customer origin Clarified that cdn.dj is a real domain name |
|
Mar 2 |
awarded | Supporter |
|
Mar 2 |
comment |
CDN CNAMEs not resolving to customer origin cdn.dj is a real domain. It's hosted in the Republic of Djibouti and I'm its proud owner. I see your point about the wild card, and I've removed it, but I actually have a CDN set up from donaldjenkins.com in the same Edgecast account, which worked without issues despite the fact donaldjenkins.com has the same wild card in its DNS |
