feature in the server to receive & send serialized (JSON encoded) objects?
If the expected, exact content type is specified on both server and receiver, I don't see why
ContentNegotiation
needs to be a hard requirement - I thought this was only about dynamically negotiating a variable content & type at run-time?
d
Dico
06/16/2019, 2:01 AM
It's not necessary. You can do this for example without installing the feature: