Incorporate clj-http-fake

I think it'd make sense for clj-http to ship with something like this, otherwise it's kinda hard to test a highly customized HTTP client.

You can write your own client and then wrap with the middleware (this is basically what clj-http-fake does). Hopefully that will let you test what you want. I do this in the tests:

(let [client (fn [req] ;; An example client function that returns whatever you need
               (if (= "example.com" (:server-name req))
                 {:status 302
                  :headers {"location" "http://example.net/bat"}}
                 {:status 200
                  :req req}))
      ;; Wrap the client with whatever middleware you want to test
      r-client (-> client client/wrap-url client/wrap-redirects)
      ;; Use the wrapped client with the regular parameters you would usually use
      resp (r-client {:server-name "example.com" :url "http://example.com"
                      :request-method :get})]

You should be able to test your middleware the same way, does that work for you?

However, it's 2 years old which I'd consider this un-maintained, it's might even be out of sync with clj-http.

I don't know how out of date it is (I haven't used it in a while). I would say right now that I don't think we should add it in to clj-http since it only increases the maintenance burden.

dakrone / clj-http

Incorporate clj-http-fake #484