Clojurians Log v2

Noob here.. I'm trying out duct example here <https://circleci.com/blog/build-a-clojure-web-app-using-duct/>. Everything works splended! So, I added a new handler to delete a film ..just as basic handler which takes a movie name and calls jdbc/execute to delete the record. But when I try to call it using httpie I get an error "Invalid anti-forgery token". The config uses :duct.module.web/site which sets the :anti-forgery key to true under :duct.middleware.web/defaults . I suspect this is the cause of the error. Is there any way to disable the check only for DELETE ..since delete is not called from a form but rather from the list of films being displayed on the page. Or is there a better way of doing this ? Hope I'm making sense 🙂

Well the best practice is to make the DELETE to also pass the anti forgery token. This means that you must have the token in the lists page. You can accomplish that by embedding the token in a meta tag and retrieve it through JS (assuming that the calls are done with XHR).

Hi, just trying to use Aleph and Yada from duct - I'm getting the error below, which I assume is because returning a manifold deferred is breaking the default middleware. Is there a way that I can switch off the default middleware ?

java.lang.ClassCastException: class manifold.deferred.Deferred cannot be cast to class clojure.lang.Associative (manifold.deferred.Deferred is in unnamed module of loader clojure.lang.DynamicClassLoader @237563b0; clojure.lang.Associative is in unnamed module of loader 'app')
                   RT.java:823 clojure.lang.RT.assoc
                  core.clj:191 clojure.core/assoc
                 core.clj:6169 clojure.core/assoc-in
                 core.clj:6161 clojure.core/assoc-in
               response.clj:79 ring.util.response/header
               response.clj:76 ring.util.response/header
              response.clj:180 ring.util.response/content-type
              response.clj:176 ring.util.response/content-type
           content_type.clj:16 ring.middleware.content-type/content-type-response

Yes, you can override the middleware. If you print out the config variable in the REPL, you can see all the middleware that is added by the web module.

Alternatively, you can write a wrapper around your handler that converts it from an Aleph-compatible handler to a Ring-compatible handler, then write another middleware that converts it back before it hits Aleph.

Ok, thanks, so I assume that this is the key that I want to override ?

:duct.handler/root
 {:router {:key :duct/router},
  :middleware
  [{:key :duct.middleware.web/not-found}
   {:key :duct.middleware.web/defaults}
   {:key :duct.middleware.web/log-requests}
   {:key :duct.middleware.web/log-errors}
   {:key :duct.middleware.web/stacktrace}]}

:duct.handler/root {:middleware []}

FYI in the end I switched off the web module and just used the web server key. Thanks for you help!