The next version of Ferron 2 will support environment variable placeholders (thank you "rousbound" on GitHub!).
We still have quite some improvements to backport from Ferron 3 beta though...
We couldn't reproduce the OOM with Ferron 2, but we found that memory usage increased (by several megabytes), but not too much...
We tried the Pingora POC, since Ferron 2 uses "h2" (indirectly) for HTTP/2, which is the same library used by Pingora...
Introducing HTTP/2 Bomb: a remote DoS in nginx, Apache httpd, Microsoft IIS, Envoy, and Cloudflare Pingora. A single client pins 32GB of server memory in 10s. Found by Codex.
Blog post: https://t.co/WO9MeExoun
PoCs: https://t.co/NpVgEHBHPl
π§ Starting today, there would be no activity for Ferron projects until a week later.
We believe solo maintainers' (such as Ferron's) well-being matters more than whether they would respond fast... We don't want the maintainers to burn out.
π§ Starting today, there would be no activity for Ferron projects until a week later.
We believe solo maintainers' (such as Ferron's) well-being matters more than whether they would respond fast... We don't want the maintainers to burn out.
Subtle performance differences in web server localhost benchmarks don't matter.
What matters is the correctness under edge cases, and how well the infrastructure could withstand the clients' load.
@K19Unknown@Sujay__Raj In our case, there would be a Microsoft Defender SmartScreen warning, because our binaries for Windows aren't digitally-signed... π₯²