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
We started using the Katharsis Client in our tests and noticed something weird when trying to handle errors and map them back to the original exception.
After some debugging, we realised the client refuses to handle the server response because of a content type header mismatch: in io.katharsis.client.internal.AbstractStub:90, it expects the content type to be exactly application/vnd.api+json, whereas the server returns application/vnd.api+json;charset=UTF-8, as set in io.katharsis.spring.KatharsisFilterV2:144.
In addition to being incoherent between the client and the server, this looks non-compliant with the spec, which is very strict about how clients and servers are supposed to behave regarding content negociation.
(We're using Katharsis 3.0.2)
The text was updated successfully, but these errors were encountered:
gilles-gosuin
changed the title
Content type management not compliant with JSON API spec
Client/Server content type management incoherent and not compliant with JSON API spec
Jun 30, 2017
We started using the Katharsis Client in our tests and noticed something weird when trying to handle errors and map them back to the original exception.
After some debugging, we realised the client refuses to handle the server response because of a content type header mismatch: in
io.katharsis.client.internal.AbstractStub:90
, it expects the content type to be exactlyapplication/vnd.api+json
, whereas the server returnsapplication/vnd.api+json;charset=UTF-8
, as set inio.katharsis.spring.KatharsisFilterV2:144
.In addition to being incoherent between the client and the server, this looks non-compliant with the spec, which is very strict about how clients and servers are supposed to behave regarding content negociation.
(We're using Katharsis 3.0.2)
The text was updated successfully, but these errors were encountered: