mirage
cohttp-eio: Content-Type header
https://www.rfc-editor.org/rfc/rfc9110#section-8.3
A sender that generates a message containing content SHOULD generate a Content-Type header field in that message unless the intended media type of the enclosed representation is unknown to the sender.
Check Server and client include Content-Type headers as required.
You don’t know a priori what is the content. I think we should leave it to the library users to do
Yes, I agree. This is mostly a check point for me to check if Content-Type headers are added to some responses or request we expose from the cohttp-eio library, e.g. https://github.com/mirage/ocaml-cohttp/blob/master/cohttp-eio/src/cohttp_eio.mli#L67