grown weary of caddy's weird config syntax, i'm migrating everything back to haproxy's weird config syntax
this time around i'm plugging iocaine into its "stream processing offload engine." but it is behaving in a nonsensical way. i'm sure it's my insufficient understanding but, it sure is violating principle of least surprise
i want a caddy/haproxy replacement that is configuration-free, instead you define its behavior in code with the help of a bunch of library functions
woo, i figured out what my haproxy/iocaine problem was. or more accurately, i jiggled it a lot more and my problem went away
and now! i finished my upgrade to iocaine 330, and flipped on the firewall feature!!
🔥 🔥 🔥
whereupon the number of tcp sockets the scrapers were holding open on my vps... increased???
i have a hypothesis as to why, and a workaround. opened an issue to document the experience. with no other changes, over time i should see fewer and fewer scrapers able to reach my sites
a very weeny construct 💀
Glyph