You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected the response content-type to be the content type specified in assumingTheDefaultContentType(...), as there is to my knowledger no way to specify the response content-type in any other way at the moment (The concept of a HttpMateChainKeys.RESPONSE_CONTENT_TYPE separate from HttpMateChainKeys.CONTENT_TYPE does not exist yet).
The text was updated successfully, but these errors were encountered:
Describe the bug
in MapMateSerializerAndDeserializer at line 93, the content-type of the response is hijacked by the content-type of the request (if present).
This leads to awkward behaviour. For example, in the case where the incoming request is application/x-www-form-urlencoded, and I've configured
httpmate.assumingTheDefaultContentType(ContentType.json())
httpmate attempts to marshall the response to
application/x-www-form-urlencoded
, which is not the expected behaviour.To Reproduce
Expected behavior
Expected the response content-type to be the content type specified in assumingTheDefaultContentType(...), as there is to my knowledger no way to specify the response content-type in any other way at the moment (The concept of a HttpMateChainKeys.RESPONSE_CONTENT_TYPE separate from HttpMateChainKeys.CONTENT_TYPE does not exist yet).
The text was updated successfully, but these errors were encountered: