We currently don't support relaying events to subscribers with any other Content-Type than application/json. You will get a 400 is you subscribe with any other Content-Type. See SubscriptionConfigValidator
Possible other types we could/should support would be at least: application/x-www-form-urlencoded as well as application/json
That's because right now we are using a JsonServiceClient (wrapped inside the ServiceClient class) to do our relay of events. That would have to change. For example, using the HttpClient instead.
We currently don't support relaying events to subscribers with any other
Content-Type
thanapplication/json
. You will get a 400 is you subscribe with any otherContent-Type
. SeeSubscriptionConfigValidator
Possible other types we could/should support would be at least:
application/x-www-form-urlencoded
as well asapplication/json
That's because right now we are using a
JsonServiceClient
(wrapped inside theServiceClient
class) to do our relay of events. That would have to change. For example, using theHttpClient
instead.