This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-12-30
Channels
- # aleph (25)
- # announcements (20)
- # babashka (29)
- # babashka-sci-dev (12)
- # beginners (27)
- # biff (3)
- # clojure (29)
- # clojure-europe (21)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojurescript (3)
- # clr (5)
- # code-reviews (4)
- # data-science (7)
- # datahike (6)
- # datascript (3)
- # emacs (9)
- # fulcro (5)
- # graalvm (10)
- # malli (15)
- # nbb (7)
- # off-topic (17)
- # pathom (9)
- # polylith (4)
- # practicalli (15)
- # reitit (3)
- # releases (2)
- # rum (1)
- # shadow-cljs (73)
- # squint (34)
- # tools-deps (3)
- # xtdb (11)
Well, you learn something every day. If an exception is thrown and handled by the exception handlers, the original request is used, not a request that has been augmented by any middleware unless you make the middleware a "global" middleware
I want to use Ring’s anti-forgery middleware (`wrap-anti-forgery`) with the built-in session middleware (`wrap-session`) and apply it to only selected routes (e.g. /
but not /api
). If I use the :reitit.middleware/registry
option and add them via :middleware
on certain routes, will that create individual, separate sessions for each route? Or should I be using the :data
option?
Nevermind, I see this issue: https://github.com/metosin/reitit/issues/205