Currently both DIN and ININ input API methods require a Content-Type HTTP header to determine the type of data being posted. In some situations the device/service posting data is not able to provide this header, or provides an inappropriate value. It would be helpful if the Endpoint configuration supported an "implicit request Content-Type" setting, which would force the value to a specific value.

Similarly for the response, both DIN and ININ currently require a request Accept HTTP header to determine what type of data to return in the response. In some situations the Accept header cannot be provided, or provides an inappropriate value. It would be helpful if the Endpoint configuration supported an "implicit response Content-Type" setting, which would force the value to a specific value.