Sounds like your authorization isn't allowing POST requests?

Does anyone have any experience deploying yada on ec2 instances? I've been able to run the jar on my test server, but when I change the name to the configt file to use either the private hostname or ip, I don't get any of the usual messages when I run it nor can I connect to it in the browser. Unfortunately I don't have access to the box, so I'm having to ask the client to open ports or change security settings

Hi all. Is it possible to use the yada.yada/response-for with a resource? E.g. something like (yada.yada/response-for ["/foo" (yada.yada/resource {:methods {:get {:response (fn [ctx] "hello")}}})] :get "/foo")?

The above results in {:status 406, :headers {"content-length" "18", "content-type" "text/plain;charset=utf-8"}, :body "\r\n\r\n{:status 406}\n"}, which is not really what I wanted 🙂

Why is an exception on a GET request wrapped inside this? It seems irregular from the other methods. https://github.com/juxt/yada/blob/0a8cd0a1790db6885f835e847bba80796d4f7f79/src/yada/methods.clj#L194

This makes rendering exception that you throw yourself a bit more cumbersome

@runejuhl Add :produces "text/html" to the :get

@borkdude That did the trick -- thank you!

@geek-draven yes, lots! I can help. You need to add a route-53 DNS entry and use that in the vhost section. See edge's config.edn

thanks @malcolmsparks, life was so much simpler when I only needed to worry about was processing flight data 🙂

Hey. I'm getting Context does not contain a :uri-info entry when trying to use yada/path-for.

The manual says "This feature is only available if your resources are declared in a bidi hierarchical route structure. Otherwise, the URL cannot be determined.", and I am using bidi for routing with yada here

@sickill are you using bidi's vhosts?

umm, no

That's why

You can use bidi path-for directly

ok, thx

We use bidi vhosts with just the wildcard, :*

I read manual's section 5.1.1 and it didn't mention neither vhosts or using bidi directly

ok, need to read about vhosts then 🙂

I also looked at https://github.com/juxt/yada/blob/master/examples/phonebook/src/phonebook/api.clj and https://github.com/juxt/yada/blob/master/examples/phonebook/src/phonebook/resources.clj , it uses yada/path-for but I can't see any mention of vhosts

ah, ok, it's in system.clj

looks, like I'm looking at wrong places all the time 😄

How can I test a resource including the default interceptor chains? response-for doesn’t seem to do this. Should I start a yada listener in my unit tests?

Probably the easiest way, maybe not the simple way 😜

(defmacro with-server
  “Runs resource in server and defines url for use in body”
  [resource & body]
  `(let [resource# ~resource
         vmodel# (vhosts-model [:* [“/api/foo” resource#]])
         listener# (y/listener vmodel#)
         port# (:port listener#)
         close# (:close listener#)
         ~‘url (str “:” port# “/api/foo”)]
     [email protected]
     (close#)))

I suspect you could call yada.handler/as-handler on your routes or vmodel and get a ring handler back

and then you can just call it like (my-handler <ring request map>)