This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-01
Channels
- # 100-days-of-code (5)
- # adventofcode (234)
- # aleph (13)
- # announcements (2)
- # architecture (3)
- # bangalore-clj (1)
- # beginners (312)
- # calva (7)
- # cider (6)
- # cljdoc (3)
- # cljs-dev (30)
- # cljsrn (2)
- # clojure (40)
- # clojure-austin (2)
- # clojure-dev (65)
- # clojure-greece (1)
- # clojure-italy (29)
- # clojure-kc (1)
- # clojure-russia (2)
- # clojure-uk (26)
- # clojurebridge (1)
- # clojurescript (4)
- # cursive (11)
- # data-science (1)
- # datomic (43)
- # docker (1)
- # duct (7)
- # emacs (3)
- # figwheel-main (7)
- # fulcro (8)
- # garden (3)
- # graphql (8)
- # hyperfiddle (4)
- # off-topic (10)
- # other-languages (12)
- # pathom (4)
- # portkey (1)
- # remote-jobs (3)
- # rum (8)
- # shadow-cljs (40)
- # tools-deps (68)
- # unrepl (2)
- # vim (5)
i'm having some requests mysteriously fail and i'd love to see what headers aleph actually sent
There are couple of request debugging options since the 0.4.7-alpha2 (I'm not actually sure about the version, but it's in the current master for sure). Here are the details https://github.com/ztellman/aleph/pull/401 (cc @kachayev)
I'm afraid there is nothing ready to use out of the box, but you can still add Netty's LoggingHandler
manually (just like it's done in the PR https://github.com/ztellman/aleph/pull/401/files#diff-e2d1dde5203e0962010d2fb176031b3cR418) using the :pipeline-transform
option of the connection pool https://github.com/ztellman/aleph/blob/ef331d14fabb629f94bc46b96af92b0e7d9ec37f/src/aleph/http.clj#L108. Basically you should pass a function which accepts a pipeline
as :pipeline-transform
, create a LoggingHandler
in it, and call (.addFirst pipeline "activity-logger" logger)
(just don't forget to return the pipeline itself from the passed function)