Swagger UI for browsing a REX OpenAPI document. Every asset embedded at build time — zero CDN requests at runtime, no version drift between deploys, works air-gapped.
-
Updated
Sep 7, 2026 - Go
Swagger UI for browsing a REX OpenAPI document. Every asset embedded at build time — zero CDN requests at runtime, no version drift between deploys, works air-gapped.
Request and response body validation for the REX framework, with content negotiation and pluggable codecs. Unknown request-body members are rejected by default.
Metrics collection and OpenMetrics exposition for the REX framework. Bounded series count, labels escaped per spec, no external collector required.
Pluggable authentication and authorization for the REX framework. Fails closed: a requirement no registered scheme can enforce is a startup error, not a runtime warning.
Sliding-window rate limiting for the REX framework at three granularities — global, per-router and per-endpoint, most specific wins. Client identity resolves through trusted proxies, never bare RemoteAddr. Stdlib only.
Bridge extension mounting a WSX gateway onto a REX route. Forwards the event bus and shares the DI container, so one service registration serves both HTTP handlers and message handlers.
Cross-Origin Resource Sharing for the REX framework. One origin allowlist, shared with rextension-security's CSRF, applied to the router's own responses as well as your handlers'.
Health checking and dependency management for the REX framework. Liveness and readiness endpoints, with the dependency gate attaching per route rather than globally.
OpenAPI 3.1 specification generation for the REX framework. Generated from the route table itself — no reflection over handlers, no annotations, no build step.
To associate your repository with the rextension topic, visit your repo's landing page and select "manage topics."