ah this is breakage in the 0.7 branch, its ok in the 0.6 one https://cljdoc.org/d/metosin/reitit/0.6.0/api/reitit.core, possibly this cljdoc breakage is the cause https://cljdoc.org/builds/68427 which https://app.circleci.com/pipelines/github/cljdoc/builder/42233/workflows/dc9220f7-a836-4013-a9f2-06600e097b6b/jobs/58608 ctrl/merge.cljc

The uncoerced body should be in :body-params, no?

at least for Jetty, the :body is a read-once inputstream, so once sombody has parsed the body it's no longer available

I've worked around this with an early middleware that does something like (update req :body slurp)

the other middlewares know how to work with a string just as well as an inputstream

I think there was a thread about this here just a while ago

https://clojurians.slack.com/archives/C7YF1SBT3/p1683818718867439

If you're using all the reitit middlewares, including the parameters middleware you'll have the parsed body after format negotiation under body-params. Read it from there, the body key belongs to the server

Yeah, but the OP wanted the raw original request body

In the context of coercion, the impetus for the question, I assume raw means unprocessed data structures, not raw bytes as they came in over the wire

right! I assumed raw bytes since signatures were mentioned, but I might be wrong

@UK0810AQ2 That’s close to what I want… I just want a JSON body in raw text, without JSON coercion so I can use it for calculating the signature. Text is fine, raw bytes are unnecessary.

Okay, that worked perfectly. The last piece of the puzzle is how to include this middleware in the app stack but only enable it for a small set of routes. If I have conditional logic inside the middleware functions, how can I get a simple flag to that middleware?

I don’t completely understand the reitit middleware-as-data completely, but it seems I should be able to have:

:middleware [[wrap-raw-body true]]

Or something like this in the routes where it is needed. But apparently my understanding of the routing is incorrect, because I’m getting stack traces when I hit those routes.

I assume I’m configuring that middleware incorrectly.

You can define middleware per route, like

["/api/healthcheck" ;; affected only by general middleware
      {:no-doc true
       :get {:summary "Healthcheck for system status"
             :parameters {} ; Do not allow any query parameters.
             :responses {200 {:body string?}}}
       :handler (fn [_]
                  (if (db/in-sync? db)
                    {:status 200 :body "ok"}
                    {:status 503 :body "sync in process"}))}]
     ["/api"
      {:swagger {:tags ["api"]}
       :middleware [wrap-request-audit-log ;; special middleware for everything unded /api not affecting other routes
                    (api-key/create-verification-middleware get-db)
                    validate-response-with-logging]}
      ["/some-fn-under-api"
       {:put {:summary "Affected by middleware defined in previous level"
              :handler
              (fn [a]
                (put-handler/do-something a))}}]

The :middleware key is the magic and defined middlewares only apply to that level and levels below.

Thanks! I figured it out, and it’s exactly like you said. It works great now.