When I have resource like {:methods {:post {:response (fn [ctx] nil)}}} should it result in a 404?

I think returning nil from a response means 404, so yes.

Yes. Nil means 404

I don’t get why I get 200 here: https://gist.github.com/borkdude/7ce01912bd8af1dfbc868f7ba82da46b

Because your response fn is returning nil

For example. Your route may match but a parameter in the path (e.g. accno) points to a resource (e.g. bank account) that doesn't exist

I believe @borkdude is saying that it does return a 200

that is because it's a POST

Sorry I misread the problem

The semantics for post are different.

You may be adding a message to a queue, inserting a database record, anything. The default response status should be 200 OK (I believe)

ok, good to know

I see 'gzip' mentioned a few places when searching the repo. (like here https://github.com/juxt/yada/blob/e76c7b2de91dbac33c0e6e394ad2269b6cbee5fe/talks/fby-2016.org#but-you-can-do)

Is there a way to enable it?

@frozenlock I think that's just for accepting Gzip'd requests

https://clojurians.slack.com/archives/C0702A7SB/p1505094831000002

https://clojurians.slack.com/archives/C0702A7SB/p1505097367000070

@danielcompton Thanks, I'll give it a try!

@danielcompton It worked! Thanks 🙂

No problem. I have a feeling that it will compress everything, including images if you're serving them from that server

Is this a problem for caching?

not really, but it's unnecessary as images are already pretty compressed

Ah, right.

if you're caching your static assets with a CDN in front then it probably doesn't matter