Information about the running environment for the Pedestal application.

This namespace ties together the many other namespaces to make it possible to succinctly define a service and start and stop a server for that service.

Provides interceptors and support for parsing the body of a request, generally according to the content type header. This results in new keys on the request map, depending on the type of data parsed.

Deeper Pedestal<->Container integration and cooperation for HTTP handling

CSRF protection interceptor support, compatible with ring-anti-forgery

Interceptors for adapting the Java HTTP Servlet interfaces.

Jetty adaptor for Pedestal.

Extends Pedestal protocols onto Jetty container classes.

Responsible for converting incoming HttpServletRequest into a Ring-compatible request map.

Creation of routes to expose file system or classpath resources as GET-able URIs.

This namespace creates interceptors for ring-core middlewares.

Constants and utilities used when implementing a routing specification, routing definition, or router.

Implementation of the verbose routing syntax.

Clojure spec definitions related to routing descriptions and routing tables.

Home for protocols related to routes (that aren’t elsewhere for historical reasons).

Secure header settings applied in interceptors

Generic Servlet adapter that closes over its implementation functions; this dynamically creates a Servlet instance that can be used with a servlet container such as Jetty.

Support for Server Sent Events.

HTTP request tracing based on Open Telemetry.

Public API for creating interceptors, and various utility fns for common interceptor creation patterns.

The implementation of the interceptor pattern, where a context map is passed through callbacks supplied by an extensible queue of interceptors, with provisions for error handling, observations, asynchronous executions, and other factors.

Tools to help debug interceptor chain execution.

A logging wrapper around SLF4J (but adaptable to other logging systems). Primary macros are trace, debug, info, warn, and error.

Metrics functionality, built on the metrics SPI (service provider interface).

Default metrics implementation based on OpenTelemetry.

Service Provider Interface for metrics providers; protocols that providers should expose and implement.

Uses GlobalOpenTelemetry to provide defaults for metrics source and tracing source.

Pedestal testing utilities; mock implementations of the core Servlet API objects, to support fast integration testing without starting a servlet container, or opening a port for HTTP traffic.

Wrappers around Open Telemetry tracing.

Defines the TracingSource protocol, and provides implementations on nil and on OpenTelemetry’s Tracer.

Utilities needed by Pedestal containers (such as io.pedestal.http.jetty) to implement WebSocket support using default Servlet API functionality, as well as utilities for applications that make use Pedestal’s websocket support.