Subject: | 'Accept' header should have priority for the deserialization format vs. 'Content-Type' |
Conversation in #catalyst:
dandv: I'm expecting the response serialization to be based on the
Accept header, then lacking that, to fall back on the Content-Type
header. For example, a client could send a JSON request but expect a
text/plain response. I know C::C::REST doesn't work that way, but is
this assumption flawed?
confound: Accept should be primary for response serialization and
Content-Type for request deserialization, but right now Content-Type
rules in both directions