Crate zeph_gateway 

HTTP gateway for webhook ingestion with bearer-token auth and health endpoint.

zeph-gateway exposes two HTTP endpoints over a single TCP listener:

Endpoint	Method	Auth required	Purpose
/health	GET	No	Liveness check; returns uptime in seconds
/webhook	POST	Yes (if token set)	Ingest external events into the agent

Security model

• Bearer token comparison is performed in constant time via BLAKE3 + subtle::ConstantTimeEq to prevent timing-oracle attacks (see GatewayServer::with_auth).
• When no token is configured the server logs a warning. Callers are expected to enforce access control at the network layer (firewall, upstream reverse proxy) in that case.
• Payload fields are sanitised with zeph_common::sanitize before forwarding.

Rate limiting

Requests to /webhook are rate-limited per remote IP using a fixed-window counter with a 60-second window. The default ceiling is 120 requests per window and is configurable via GatewayServer::with_rate_limit. Setting the limit to 0 disables rate limiting.

Quick start

use tokio::sync::{mpsc, watch};
use zeph_gateway::GatewayServer;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let (webhook_tx, mut webhook_rx) = mpsc::channel::<String>(64);
    let (_shutdown_tx, shutdown_rx) = watch::channel(false);

    // Spawn a consumer that processes incoming webhook messages.
    tokio::spawn(async move {
        while let Some(msg) = webhook_rx.recv().await {
            println!("received: {msg}");
        }
    });

    GatewayServer::new("127.0.0.1", 8080, webhook_tx, shutdown_rx)
        .with_auth(Some("my-secret-token".into()))
        .with_rate_limit(60)
        .serve()
        .await?;

    Ok(())
}

Structs

GatewayServer

HTTP gateway server with bearer-auth, rate limiting, and body-size enforcement.

Enums

GatewayError

Errors that can be returned by the HTTP gateway.