User talk:Eighty5cacao/misc/CDN URL notes
Scratch work for Akamai
To be cited later because it mentions:
- Prior to Oct. 18, 2000 (i.e. a lot earlier than we need to worry about),
a248.e.akamai.netdid not properly verify that the origin server specified by the URL was authorized to be accessed by an Akamai client. This could have been useful for phishing.
- The official servicemark for the
a248.e.akamai.netservice tier was "FreeFlow" (TODO: is this still true today?).
- A 503 response from Akamai can indicate that the origin server has an expired certificate.
--Eighty5cacao 20:52, 4 December 2012 (MST) (last edit 22:04, 8 December 2012 (CST))
- Some searching told me that the name "FreeFlow(SM)" is not specific to the HTTPS support
and more likely refers to Akamai's DNS architecture. Also, here(PDF) is some more detailed info on the URL paths for the service tier in question. --Eighty5cacao (talk) 22:11, 8 December 2012 (CST) (last edit 22:31, 4 February 2013 (CST))
Does the Free Software Foundation have any specific suggestions for an alternative to the "content delivery network" terminology? I don't see any such alternative in the relevant section of their essay. --Eighty5cacao (talk) 22:03, 8 December 2012 (CST)
- Best guess so far: They'd probably call it a "distributed cache" (or "distributed web cache" if disambiguation were necessary). --Eighty5cacao (talk) 18:17, 22 December 2012 (CST)
Other brain dumps
- What the HTTPS Everywhere team calls a "bucket" is more commonly called a "distribution" (at least for Amazon CloudFront; cite others)
- Mention something about CloudFront's "custom SSL" support (anything special worth paying attention to?)