Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
theKarlisK516714dAnything is SO if you're stubborn enough.
Never ever use cloudflare
@Nachfolger cloudflare is literally a terrorist organization. Their anti ddos firewall platform that does external crypto can see all your ptxt traffic
Which is short for you don’t have to be a genius to know it’s an NSA way of defeating encryption. Sounds dramatic but if it isn’t that then it’s just some company doing data mining trying to defeat encryption (I say trying but I really mean succeeding) and is that really any better?
Avoid at all costs. I would cut off all my fingers and toes before using cloudflare.
Root4572914d@FrodoSwaggins and how often are most services hit by ddos's? Basically never. And what damage does it do? Often nothing at all.
It's insurance against catching a cold.
And it's free; all you have to do is let someone watch and record every move you make, every sentence you utter, every word you write.
The solution is timestamped logs on the server end, full verbosity, then see what happened.
xalys185614dYou have a plugin that causes your website to return over 10 headers.
theKarlisK516710dWe actually experienced a simillar problem at my workplace, it turned out that due to recent changes in our network the external domain landed in our central Apache proxy and then went to the actual application server, which had a NGINX proxy serving the application... normally it should just go straight to the NGINX. We ended up having 520 or 500 every few minutes, then the request would go through, then back to errors. No errors anywhere, just status codes in access logs. Probably could've been fixed by fixing Apache configs but changing where the requests go fixed our problem.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job