@malcolmsparks that would certainly be welcome here. we currently don't encrypt the traffic between our load balancers and the app server...

Right. I believe you'd need to to get through a PCI or FIPS audit

interesting read about cloudbleed

If you alter before, you get yada's shorthand expansion and validation. If you alter afterwards, you need to take a little care not to break the validation

Or revalidate

ok, so it's expansion+validation

I'll alter after, as I mostly want to set custom 404 responses

Is it straightforward to have multiple access-control schemes for a resource? Or should I create multiple routes/resources backed by the same code?

The former should be ok. Yada supports multiple auth schemes

{:access-control {:scheme #{"Basic" "My Custom Auth"}}} ?

(am currently reading the manual...)

Yes, but that's shorthand. The longhand supports a collectio

You can view the longhand by printing out a resource

You can even publish this with yada

Take a resource and wrap it in yada/handler

ah yes

I've done that accidentally before!

there isn't anything like the example project.clj for leiningen for yada resource models is there?