Changes between Version 83 and Version 84 of doc/meek


Ignore:
Timestamp:
Jul 28, 2014, 2:05:00 AM (5 years ago)
Author:
dcf
Comment:

LInks for popular CloudFront subdomains.

Legend:

Unmodified
Added
Removed
Modified
  • doc/meek

    v83 v84  
    8585  Amazon CloudFront does not cache the responses to POST, PUT, DELETE, OPTIONS, and PATCH requests – these requests are proxied back to the origin server.
    8686
    87 There's a question of what to use as the front domain. Any particular *.cloudfront.net name could be individually blockable. The generic names cloudfront.net and www.cloudfront.net don't resolve. Maybe pick one with a lot of collateral damage? Or a few, and randomly choose between them? Or connect to an IP, rather than a domain (#12208).
     87There's a question of what to use as the front domain. Any particular *.cloudfront.net name could be individually blockable. The generic names cloudfront.net and www.cloudfront.net don't resolve. Maybe pick one with a lot of collateral damage? Or a few, and randomly choose between them? Or connect to an IP, rather than a domain (#12208). Alexa has [http://www.alexa.com/siteinfo/cloudfront.net a list of the most popular cloudfront.net domains] ("Where do visitors go on cloudfront.net?"), which starts out:
     88{{{
     89d3dsacqprgcsqh.cloudfront.net   14.67%
     90deayhd4nq31b0.cloudfront.net    6.06%
     91d396qusza40orc.cloudfront.net   2.72%
     92d3v9w2rcr4yc0o.cloudfront.net   2.26%
     93d13yacurqjgara.cloudfront.net   2.09%
     94}}}
     95There's a [https://www.robtex.com/en/advisory/dns/net/cloudfront/d3dsacqprgcsqh/#shared_pa_ma list of CNAMES] that point to an example cloudfront.net subdomain, but I don't think a CNAME works for us because we need the wildcard *.cloudfront.net certificate.
    8896
    8997==== How to set up a CloudFront reflector ====