Ring Middleware in Depth
Learn how Ring middleware wraps handlers to add cross-cutting behavior like logging, parameter parsing, and session handling in Compojure web apps.
Ring Middleware in Depth is a free Clojure Functional Programming & JVM Backend Development lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Clojure Functional Programming & JVM Backend Development learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What Is Middleware?
In Ring, a handler is a function that takes a request map and returns a response map. Middleware is a higher-order function that takes a handler and returns a new handler.
This lets you wrap behavior around your core logic without modifying it.
(defn wrap-example [handler]
(fn [request]
(handler request)))The Wrapping Pattern
Every middleware follows the same shape: receive a handler, return a function that takes a request. You can act before or after calling the inner handler.
- Before: inspect or modify the request
- After: inspect or modify the response
(defn wrap-logging [handler]
(fn [request]
(println "Incoming:" (:uri request))
(let [response (handler request)]
(println "Status:" (:status response))
response)))Applying Middleware
You apply middleware by calling it on your handler. The result is a new handler that you pass to the server.
(def app
(-> handler
wrap-logging))The Threading Macro
The -> threading macro is the idiomatic way to stack middleware. Each layer wraps the one before it.
Order matters: the last middleware listed is the outermost layer that sees the request first.
(def app
(-> routes
wrap-params
wrap-session
wrap-logging))Built-in Middleware
The ring-defaults library bundles common middleware so you do not write it by hand.
- wrap-params parses query and form params
- wrap-session manages sessions
- wrap-keyword-params turns string keys into keywords
(require '[ring.middleware.defaults :refer [wrap-defaults site-defaults]])
(def app
(wrap-defaults routes site-defaults))Modifying the Request
To add data for downstream handlers, assoc a key onto the request before calling the inner handler.
(defn wrap-user [handler]
(fn [request]
(let [user (lookup-user (:session request))]
(handler (assoc request :current-user user)))))Modifying the Response
To set headers or transform output, work on the response after calling the inner handler.
(defn wrap-content-type [handler]
(fn [request]
(let [response (handler request)]
(assoc-in response [:headers "Content-Type"] "text/html"))))Conditional Middleware
Sometimes you only want middleware on certain routes. You can apply it selectively rather than globally.
(defroutes app
(GET "/public" [] public-handler)
(-> (GET "/admin" [] admin-handler)
wrap-authentication))Exception Handling Middleware
A common pattern is wrapping all handlers in a try/catch to return a clean 500 response instead of leaking stack traces.
(defn wrap-errors [handler]
(fn [request]
(try
(handler request)
(catch Exception e
{:status 500 :body "Internal Server Error"}))))Order of Execution
Think of middleware as an onion. The request travels inward through each layer to the handler, then the response travels outward back through them.
- Outermost middleware runs first on request, last on response
- Innermost runs last on request, first on response
; request: wrap-logging -> wrap-session -> wrap-params -> handler
; response: handler -> wrap-params -> wrap-session -> wrap-loggingComposing Reusable Middleware
Because middleware are just functions, you can group them into a single composed function and reuse it across multiple apps.
(defn wrap-common [handler]
(-> handler
wrap-logging
wrap-errors
wrap-params))Quick Check
Test your understanding of middleware ordering.
Recap
You learned that middleware are higher-order functions wrapping handlers to add cross-cutting behavior.
- They can modify the request before, or the response after
- The
->macro stacks them like an onion - Libraries like
ring-defaultsbundle common ones
Next you can combine custom middleware with Compojure routes for full-featured apps.
Frequently asked questions
Is the “Ring Middleware in Depth” lesson free?
Yes — the full text of “Ring Middleware in Depth” is free to read here on the web, and the Clojure Functional Programming & JVM Backend Development course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Clojure Functional Programming & JVM Backend Development course, upgrade to CoddyKit PRO.
What will I learn in “Ring Middleware in Depth”?
Learn how Ring middleware wraps handlers to add cross-cutting behavior like logging, parameter parsing, and session handling in Compojure web apps. You practise Clojure Functional Programming & JVM Backend Development with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Clojure Functional Programming & JVM Backend Development?
No prior experience is required. Clojure Functional Programming & JVM Backend Development on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Ring Middleware in Depth” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Clojure Functional Programming & JVM Backend Development lesson?
Yes. Every Clojure Functional Programming & JVM Backend Development lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Introduction to Ring & HTTP Basics
- Routing with Compojure
- Handling Requests & Responses
- Ring Middleware in Depth