QUOTE(kwss @ Dec 18 2023, 10:38 AM)
I briefly look at it, seems not so straightforward. For a start,
https://vault.bitwarden.com/api/config is just a plain GET request. But they did:
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 01 Jan 1970 00:00:01 GMT
This open themselves to DoS attack. They should have enable caching, even a mere 1 minute would allow Cloudflare to absorb all the attack, including Layer 7 attack.
Then I look at
https://developers.cloudflare.com/turnstile/Not sure how they want to do it. Reason is for the endpoint, cloudflare immediately respond:
HTTP/1.1 403 Forbidden
I suspect only with known browser string they will respond the full Turnstile page.
After looking at all this, my opinion is they should just enable caching, disable the captcha and let cloudflare take the hit.
Well, I guess it is normally they don't understand this kind of stuff, and lazy to.
Like I know a private forum which set as 45 days of caching js file, which u know, a lot method to invalidate cached file, like 1.hash.js, even clicking the flush cache in cloudflare's dashboard also count, which just taken 1 mins.
But the developer just reply me, lazy la, it is not interesting feature, so trouble, let it be....
Then after 45 days of desync/outdated js version, finally cache expired, bug fixed, lol.
Within this 45 days, a lot of repeated bug report being created, and server get DDoS by the outdated js.file by check-in repeatly, well...
And yes, now it is set as 15 days caching, and after 2 years, the private forum is, well, nearly dead now.
So, there will be more and more issues like this gonna happen in the future, as rapid development is the future, leaving bank system still running as cobol wlll not be the worst one...
---
Yes, solution is out there, with google, but, 99% of person don't know how to google properly, what's you saw is just SEO result, so...
Not gonna put a lot of hope on everything already....
Just, nah, doing my own best la...