deCloudflare/cloudflare-tor
deCloudflare/cloudflare-tor
0
0
Fork 0
mirror of https://git.sdf.org/deCloudflare/cloudflare-tor synced 2024-12-26 07:53:26 +01:00
Code Issues Releases Activity

Merge branch 'master' of mia07/cloudflare-tor into master

Browse Source
This commit is contained in:
Jeff Cliff 2019-03-02 17:56:57 +00:00 committed by Gogs
commit 7caccce93f
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
what-to-do.md
View File

@ -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_.