Middleware for automatically adding a content type to response maps.

Middleware for parsing and generating cookies.

Middleware to serve files from a directory.

Most of the time you should prefer ring.middleware.resource instead, as this
middleware will not work with files in jar or war files.

Middleware to add Last-Modified and Content-Type headers to file responses.

This middleware is deprecated. Prefer the ring.middleware.content-type and
ring.middleware.not-modified middleware instead.

Middleware that adds session-based flash store that persists only to the
next request in the same session.

Middleware to simplify replying to HEAD requests.

A response to a HEAD request should be identical to a GET request, with the
exception that a response to a HEAD request should have an empty body.

Middleware that converts parameter keys in the request to keywords.

Middleware that parses multipart request bodies into parameters.

This middleware is necessary to handle file uploads from web browsers.

Ring comes with two different multipart storage engines included:

  ring.middleware.multipart-params.byte-array/byte-array-store
  ring.middleware.multipart-params.temp-file/temp-file-store

A multipart storage engine for storing uploads as in-memory byte arrays.

A multipart storage engine for storing uploads in temporary files.

Middleware to convert a single-depth map of parameters to a nested map.

Middleware that returns a 304 Not Modified response for responses with
Last-Modified headers.

Middleware to parse url-encoded parameters from the query string and request
body.

Middleware for serving static resources.

Middleware for maintaining browser sessions using cookies.

Sessions are stored using types that adhere to the
ring.middleware.session.store/SessionStore protocol.
Ring comes with two stores included:

  ring.middleware.session.memory/memory-store
  ring.middleware.session.cookie/cookie-store

A session storage engine that stores session data in encrypted cookies.

A session storage engine that stores session data in memory.

Contains the protocol used to define all Ring session storage engines.

Utility functions for handling I/O.

Utility functions for determining the mime-types files.

Regular expressions for parsing HTTP.

For internal use.

Functions for augmenting and pulling information from request maps.

Functions for generating and augmenting response maps.

Utilities for testing Ring components.

All functions in this namespace are currently deprecated.

Functions for dealing with time and dates in HTTP requests.

Protocols and utility functions for websocket support.