Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Unifying Accept/Content-Type headers #27

Closed
jcantosz opened this issue Jan 6, 2017 · 1 comment
Closed

Unifying Accept/Content-Type headers #27

jcantosz opened this issue Jan 6, 2017 · 1 comment
Assignees
Milestone

Comments

@jcantosz
Copy link
Contributor

jcantosz commented Jan 6, 2017

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

@v1r3n
Copy link
Contributor

v1r3n commented Jan 9, 2017

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

@v1r3n v1r3n closed this as completed Jan 11, 2017
@v1r3n v1r3n added this to the 2017 Q1 milestone Jan 11, 2017
@v1r3n v1r3n self-assigned this Jan 11, 2017
amoutaux pushed a commit to Mobeye/conductor that referenced this issue Mar 29, 2022
Fix CI build issues (related to publishing snapshots)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants