This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-12
Channels
- # beginners (34)
- # boot (14)
- # cider (2)
- # cljs-dev (21)
- # cljsrn (1)
- # clojure (31)
- # clojure-android (10)
- # clojure-spec (12)
- # clojure-uk (3)
- # clojurescript (64)
- # cursive (31)
- # data-science (9)
- # datomic (27)
- # fulcro (11)
- # graphql (14)
- # jobs (1)
- # leiningen (1)
- # lumo (27)
- # off-topic (65)
- # om (2)
- # onyx (77)
- # pedestal (1)
- # re-frame (4)
- # shadow-cljs (6)
- # vim (1)
- # yada (3)
Hi everyone, if a client requests an unsupported content type on a yada resource does yada supply a default representation of the content? If so, instead of using a default is it possible to support responding with a http 406 and a payload of the supported content types? I can do this easy enough but wanted to check I've not missed something already built into yada?
Don't have time to check code, but I think if you request a content type not provided (and don't provide fallbacks) you'll get a 406
Thanks for the reply, I did have a quick look, it looks to me like the content representations checking happens only for HEAD & GET requests. I could be reading it wrong though. I was expecting the same behaviour with the response from a POST.