This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-08
Channels
- # atlanta-clojurians (1)
- # beginners (116)
- # cider (70)
- # cljs-dev (11)
- # cljsrn (2)
- # clojure (218)
- # clojure-italy (7)
- # clojure-nl (14)
- # clojure-nlp (11)
- # clojure-spec (8)
- # clojure-uk (113)
- # clojurescript (86)
- # core-async (14)
- # cursive (24)
- # datomic (64)
- # duct (1)
- # emacs (3)
- # fulcro (20)
- # graphql (10)
- # jobs-rus (1)
- # london-clojurians (1)
- # luminus (1)
- # nyc (1)
- # off-topic (24)
- # onyx (1)
- # parinfer (1)
- # pedestal (14)
- # portkey (11)
- # re-frame (36)
- # reagent (9)
- # reitit (5)
- # ring (1)
- # shadow-cljs (197)
- # spacemacs (21)
- # specter (22)
- # sql (15)
- # tools-deps (5)
I’m incredibly stoked for the potential of vase + ions. I’ve tried (multiple times if I’m being honest) to get vase + datomic cloud to work before, but to no avail. Is there any discussion happening about combining vase + ions?
@joe.lane nothing concrete but I’m sure it will happen. I’ll keep folks posted here once I have more information.
Interceptors I took from an example are io.pedestal.http.body-params/body-params
and io.pedestal.http/html-body
.
But my response header still includes Content-Security-Policy: object-src 'none'; script-src 'unsafe-inline' 'unsafe-eval' 'strict-dynamic' https: http:;
.
@twashing you can pass ::http/secure-headers {:content-security-policy-settings {:object-src "'none'"}}
or similar in the service map
Hmm, that doesn’t quite work. But I think it’s close… Now I can’t find any reference in the docs. http://pedestal.io/reference/index#_securing_a_pedestal_application
@martinklepsch Thanks btw :)
some of it is documented here: http://pedestal.io/reference/service-map
Some other I dug out of this mailing list thread: https://groups.google.com/forum/#!topic/pedestal-users/caRnQyUOHWA
@martinklepsch Did the trick. Thanks mate!