Update 'what-to-do.md'
This commit is contained in:
parent
c9d59a5a35
commit
4c8eb299f2
|
@ -92,6 +92,8 @@ If Cloudflare leak your information, it's not our fault. [*]
|
|||
|
||||
- Using Cloudflare will increase chances of an outage. Visitors can't access to your website if your server is down *or Cloudflare is down*. Did you really think [Cloudflare never go down](https://www.ibtimes.com/cloudflare-down-not-working-sites-producing-504-gateway-timeout-errors-2618008)? Another [sample](https://twitter.com/Jedduff/status/1097875615997399040).
|
||||
|
||||
- Using Cloudflare to proxy your "API service" will harm your customer. A customer called you and said "I can't use your API anymore", and you have no idea what is going on. Cloudflare can silently block your customer. [Do you think it is okay](https://twitter.com/Skyfusion89/status/1101596592426151937)?
|
||||
|
||||
- Do you need HTTPS certificate? Use "[Let's Encrypt](https://letsencrypt.org/)" or just buy it from CA company.
|
||||
|
||||
- Install Web Application Firewall (such as OWASP) and Fail2Ban on _your_ server and configure it _properly_.
|
||||
|
|
Loading…
Reference in New Issue