Fork me on GitHub
#yada
<
2017-11-12
>
markwoodhall08:11:57

Hi everyone, if a client requests an unsupported content type on a yada resource does yada supply a default representation of the content? If so, instead of using a default is it possible to support responding with a http 406 and a payload of the supported content types? I can do this easy enough but wanted to check I've not missed something already built into yada?

danielcompton22:11:10

Don't have time to check code, but I think if you request a content type not provided (and don't provide fallbacks) you'll get a 406

markwoodhall23:11:29

Thanks for the reply, I did have a quick look, it looks to me like the content representations checking happens only for HEAD & GET requests. I could be reading it wrong though. I was expecting the same behaviour with the response from a POST.