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
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
I would like to construct all messages to and parse all messages from the conductor in the same fashion. Can we make all Accept and Content-Type headers accept application/json? Some responses are of type text/plain which means I must do extra work (or have a good memory) to create my microservices
The text was updated successfully, but these errors were encountered:
Good suggestions. However, if you are using REST client libraries like Spring or Jersey, they take care of it automatically - without additional work required.
Update:
Streamlined APIs to support application/json as content-type in the following commit: bdcc253
I would like to construct all messages to and parse all messages from the conductor in the same fashion. Can we make all
Accept
andContent-Type
headers acceptapplication/json
? Some responses are of typetext/plain
which means I must do extra work (or have a good memory) to create my microservicesThe text was updated successfully, but these errors were encountered: