From 19a934493e8428aa8bc91aed957546cee4d0ac1c Mon Sep 17 00:00:00 2001
From: Liam Reese <85e55ba2d11629480a882a788f4dbd1743cca041@cloudflare.com>
Date: Thu, 27 May 2021 03:30:04 +0000
Subject: [PATCH]

---
 subfiles/people.twitter.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/subfiles/people.twitter.md b/subfiles/people.twitter.md
index c207f3a5..1ade3ce3 100644
--- a/subfiles/people.twitter.md
+++ b/subfiles/people.twitter.md
@@ -7,6 +7,7 @@
 
 
 
+- yup this one. and cloudflare response as a normal HTML page and wihtout cors. even CF has CORS, the front end wont be able to read the message also as they didnt do error handling for that. ([ooijiyoung](https://twitter.com/ooijiyoung/status/1397745031230889985))
 - isu CORS tu hanya 'side effect' kpd mslh lain, mungkin org bkn infra/dev nampak error ni. Most of it related to redirected url daripada response yg triggered by cloudflare. Main issue still related dgn rate-limiting tadi. ([meorajrul](https://twitter.com/meorajrul/status/1397597919335702537))
 - Please explain how you guys dev this website? No need to argue with AZ one for yesterday , your API is totally down for whole hour when some of them lucky until can register without Cloudflare Rate Limiting and your API Server Error 429 / 503 / CORS Policy ([sleong123](https://twitter.com/SLeong123/status/1397706657962991617))
 - 70mil is way too much for such error. The Cloudflare can’t even handle the access surge. API are not configured properly. Editing code on the live server? Come on la. Only noobs does that. ([measaura](https://twitter.com/measaura/status/1397590233911201797))