This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-12
Channels
- # aleph (1)
- # announcements (13)
- # asami (4)
- # babashka (47)
- # beginners (22)
- # calva (11)
- # circleci (1)
- # clj-kondo (14)
- # clojure (43)
- # clojure-europe (43)
- # clojure-gamedev (1)
- # clojure-nl (1)
- # clojure-uk (6)
- # clojurescript (13)
- # core-async (5)
- # cursive (8)
- # datomic (20)
- # events (3)
- # fulcro (12)
- # graalvm (1)
- # graphql (4)
- # gratitude (3)
- # java (2)
- # juxt (2)
- # leiningen (12)
- # off-topic (30)
- # pathom (33)
- # pedestal (5)
- # podcasts-discuss (1)
- # polylith (14)
- # rdf (2)
- # re-frame (12)
- # reagent (3)
- # releases (2)
- # shadow-cljs (24)
- # spacemacs (13)
- # sql (2)
- # tools-build (16)
@frwdrik Thanks! I wasn’t expecting it to be to be this simple. So I gather that the content-type negotiation logic is the same as for language negotiation?
According to that link you mentioned, the "Accept-Languge" header uses https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation
Listed on that page is several "Accept-*" headers that the server can negotiate on. But I believe it ultimately is up to the server to choose exactly which negotiation strategy it wants to use. For Apache, check out https://httpd.apache.org/docs/current/en/content-negotiation.html#algorithm