This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-11
Channels
- # aleph (7)
- # announcements (5)
- # beginners (58)
- # calva (20)
- # cider (10)
- # clj-kondo (4)
- # cljfx (5)
- # cljsrn (7)
- # clojure (29)
- # clojure-europe (11)
- # clojure-mexico (1)
- # clojure-norway (26)
- # clojure-uk (9)
- # clojurescript (1)
- # cursive (31)
- # datahike (22)
- # datomic (12)
- # duct (3)
- # fulcro (28)
- # helix (35)
- # hyperfiddle (28)
- # lsp (4)
- # malli (8)
- # midje (3)
- # music (2)
- # nbb (9)
- # nrepl (20)
- # off-topic (36)
- # polylith (3)
- # shadow-cljs (47)
- # sql (2)
- # testing (7)
- # vim (17)
- # xtdb (7)
Is there a way to increase the timeout of an endpoint in module.duct.web?
(note: maybe the issue is not a duct timeout, but somewhere in the code in the handler that calls external api)
I would say that the timeouts are configured in the HTTP server you are using. Unless you configured your Duct project otherwise, jetty is used by default. So it's either a Jetty configuration setting (which may or may not be exposed through duct/server.http.jetty
, and may or may not be available in ring/ring-jetty-adapter
). Or if you are using a reverse proxy (like nginx, or AWS ElasticLoadBalancer, etc) in front of your HTTP server, you may need to configure the timeout in there.