Julius Kiekbusch
@julius-kiekbusch.de
Software Engineer and IT-Consultant specialized in the Laravel Ecosystem.
Or do it like cloudflare which blocked http at the tcp level by blocking port 80.
blog.cloudflare.com/https-only-f...
blog.cloudflare.com/https-only-f...
HTTPS-only for Cloudflare APIs: shutting the door on cleartext traffic
We are closing the cleartext HTTP ports entirely for Cloudflare API traffic. This prevents the risk of clients unintentionally leaking their secret API keys in cleartext during the initial request, be...
blog.cloudflare.com
September 29, 2025 at 1:30 PM
Or do it like cloudflare which blocked http at the tcp level by blocking port 80.
blog.cloudflare.com/https-only-f...
blog.cloudflare.com/https-only-f...
It is like a secret key! The longer the better! Makes it even harder to differentiate between the real email address and a scam email address! 🫣
July 17, 2025 at 3:46 AM
It is like a secret key! The longer the better! Makes it even harder to differentiate between the real email address and a scam email address! 🫣
This needs a more in depth explanation 😂
April 30, 2025 at 8:15 PM
This needs a more in depth explanation 😂
Would you handle some specifics different if you were to use SSO only? I think only the login (maybe the logout) event makes sense. Do you include 2fa in the login failed events? (Probably need another event for that)
December 4, 2024 at 5:25 AM
Would you handle some specifics different if you were to use SSO only? I think only the login (maybe the logout) event makes sense. Do you include 2fa in the login failed events? (Probably need another event for that)