4 ms·

Please remember that CloudFlare is a sort of reverse proxy with some network protections and enhancements. If your infrastructure is unavailable, users won't g

• otterley 12y ago
  CloudFlare can serve cached responses in the event that your origin server is unavailable. This is particularly useful for static websites, but that's not the most common use case.
  • jonknee 12y ago
    In the use case for keyless SSL the caching is pretty useless. Banks (what the article described as the reason this was created) are interactive. They want CloudFare to block the DDOS while letting their customers through. The DDOS attackers aren't firing legit requests (sign-in attempts or whatever) and would never make it through to the SSL handshake.
  • peterwwillis 12y ago
    If your origin server can be found on the internet, it can be DDoS'd/attacked, and your (dynamic) site will go down. This is true of all CDNs. The way to avoid this is to either have the CDN host your app servers or provide a private connection from your origin to the CDN. I guess technically the TLS-secured static content would now be at more risk than it was before, when the cached content would have been served. But existing session tickets would probably be honored, so only new clients would get rejected. Still, it's a tradeoff some people would probably be fine with.
    • deleted 12y ago
      [deleted]