This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-28
Channels
- # aws-lambda (2)
- # beginners (49)
- # boot (49)
- # cider (7)
- # clara (1)
- # cljsrn (4)
- # clojure (199)
- # clojure-android (49)
- # clojure-dev (1)
- # clojure-greece (4)
- # clojure-italy (3)
- # clojure-nl (4)
- # clojure-norway (5)
- # clojure-russia (78)
- # clojure-spec (22)
- # clojure-uk (18)
- # clojurebridge (2)
- # clojurescript (252)
- # core-typed (2)
- # cursive (11)
- # data-science (1)
- # datascript (2)
- # datomic (38)
- # devcards (1)
- # flambo (3)
- # hoplon (10)
- # immutant (2)
- # jobs (3)
- # luminus (1)
- # lumo (2)
- # off-topic (8)
- # om (3)
- # onyx (29)
- # parinfer (1)
- # pedestal (4)
- # portkey (13)
- # re-frame (13)
- # reagent (6)
- # ring (3)
- # ring-swagger (15)
- # schema (2)
- # spacemacs (4)
- # test-check (4)
- # untangled (46)
- # yada (2)
Heya, let's say I have a handler which will respond via as-channel
and thus send a Transfer-Encoding: chunked
header on GET
rather than a Content-Length
header. Now I want that handler to respond the same way to a HEAD
request, of course. However, I can't find a way to achieve that, immutante.web
always adds a Content-Length
header unless I go through as-channel
, too, and don't close the channel right in the :on-open
callback. Any hints?
That is, keeping the channel open beyond the :on-open
callback indeed produces a Transfer-Encoding: chunked
header but then I have to have some mechanism that cleans up those dummy channels afterwards which I would like to avoid 🙂