Blog Posts
Published 27 articles
BlakeGate : the missing control plane for ProxyAuth infrastructure
ProxyAuth protects applications at the data plane. BlakeGate is the vision for the control plane above it: managing infrastructure, deploying cryptographic trust material, synchronizing accounts, applying live configuration updates and coordinating multiple ProxyAuth instances without turning the gateway itself into an administration monolith.
Wildcard vhosts: one label, exact names first, and if_vhost to keep them in one group
A vhost entry can be a pattern like *.example.com. It covers exactly one extra label, always yields to a name declared explicitly, and — since 1.2.7 — can share a group with the apex thanks to per-request precedence and if_vhost. Here is the matching rule, the bug that shaped it, and how certificates constrain it.
How ProxyAuth tests itself: a deep gate on every pull request, a wide one on every merge
Two CI pipelines answer two different questions. The pull-request gate asks whether a change is safe to let in — lint, full test suite, a real instance under attack, a stress test that fails on regression, and a dependency audit. The main-branch pipeline asks whether the system still builds and runs on six Linux distributions. Here is each step and why it exists.
streaming and backend_timeout: what buffering really costs, and the gap streaming leaves
By default ProxyAuth collects a whole response before sending a byte. streaming relays it as it arrives — essential for git forges, registries and event streams. Here is exactly what changes, when ProxyAuth buffers anyway, and how backend_timeout means two different things depending on which mode a route is in.
IP abuse blocklists: the first gate, and the one setting that makes it inert
ProxyAuth can load Spamhaus, FireHOL, AbuseIPDB exports or your own files and refuse listed addresses before routing even starts. Here is how sources are parsed, cached and refreshed — and why, behind a load balancer, one missing line in config.json turns the whole feature into a no-op.
sync, in groups: build constants as a trust boundary, not just a deployment chore
Two ProxyAuth builds do not validate each other's tokens until you make them. That is usually described as an obstacle before multi-node SSO works — read the other way, it is a segmentation primitive most gateways do not have. Here is exactly what sync export and sync import move, how to form groups on purpose, and the gaps that remain.