Response headers are necessary in order to declare content type.
From this perspective, we need to have an additional consideration.
When content-type is application/json we should be sending a default header for that, but that is a bit of a reach, the library isn't really for that. Instead, we should enforce the typing of such headers, and make the user meet the contract.
If they wished to always provide that header, they could do so with a custom responder that returns that header.
Response headers are necessary in order to declare content type.
From this perspective, we need to have an additional consideration.
When content-type is
application/json
we should be sending a default header for that, but that is a bit of a reach, the library isn't really for that. Instead, we should enforce the typing of such headers, and make the user meet the contract.If they wished to always provide that header, they could do so with a custom responder that returns that header.
closes: #24