News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by TedDoesntTalk on Wednesday November 18, 2026 @04:20PM (#50552267)
Envoy probably has the advantage that it’s only a reverse proxy server, unlike nginx which has other uses too like a general-purpose web server with optional modules.
Re:Pre-auth RCE in Nginx HTTP/2 handling by weitendorf on Wednesday November 18, 2026 @04:46PM (#50552608)
You can implement custom http filters for envoy or use this for general web serving: https://www.envoyproxy.io/docs/envoy/v1.15.2/configuration/h...

The documentation, DX/UX, and discoverability for these features are pretty bad. But they work well if you know how to do it.

Implementing a custom HTTP filter itself is actually easy, I can share examples I did in the last year for a voice inference stack if anybody is interested. The problem is just that the devloop is very painful, because Envoy doesn't make it easy to know why something isn't working (this is actually most of what I did with it at Google, tons of testing/verification and compatability infra for relatively simple http stuff) and the builds take a very long time.

Re:Pre-auth RCE in Nginx HTTP/2 handling by technion on Wednesday November 18, 2026 @05:04PM (#50552862)
On all my small projects (eg rails apps) the reverse proxy to the app servers is the same server expected to serve the static assets directly. In fact the majority of bot nonsense never goes through the proxy due to path rules.

Envoy is only attractive at a higher scale.