gRPC and WebSocket support, more control over authentication and streams, and rate limits shared between gateway instances with Redis.
Breaking and behavior changes
RefuseOnMissingandRefuseOnExpiredwere removed from auth methods, a config that still has them is rejected. Bothtrue: delete both lines, same behavior.RefuseOnMissing: false: useAllowAnonymous: true.RefuseOnExpired: false: no replacement, expired tokens are always refusednocleye checknow exits with failure when the config has errors. Warnings alone still exit with success- Any
Upgradethat is not a valid WebSocket handshake is refused with400 - New default limits on servers (timeouts and a maximum request body size). Long or slow traffic can be affected, check the defaults and how to turn them off in the docs
request_size_bytesin the access log is now the bytes really read, andgw_requests_totalhas a newgrpc_statuslabel
New features
- gRPC support, plaintext and TLS, unary and streaming. Every call is authenticated and rate limited on its own
- WebSocket support (HTTP/1.1)
- Protocol blocks on servers (
HTTP,GRPC,WebSocket) to combine protocols on one server and tune timeouts and limits per protocol - Authentication:
AllowAnonymous,RemoveCredentialHeaderandForwardClaims X-Nocleye-AuthenticatedandX-Nocleye-User-Idheaders on proxied requests- Stream observability: new access log fields, access log rule filters and metrics for streams
- Shared limits with Redis. Usage control rules can keep their counters in a Redis-compatible server, so all gateway instances share one limit
nocleye checkcovers all of the above
Fixes
- Graceful shutdown and config swaps now handle open streams and connections cleanly
- The in-flight gauge no longer stays high after an aborted response
Customheader mode keeps the headers that gRPC and WebSocket need
Security
X-Nocleye-*headers sent by clients are always dropped, so they cannot be forged- The
Upgradeguard closes the h2c smuggling path - Body size limit, idle timeouts and stream limits bound slow and abusive clients
- Redis credentials can only be given as
env:orfile:references - Beta limits (WebSocket and long gRPC streams authenticated once, Redis limits restarting from zero on every upgrade): check the details in the docs
