Skip to content
This repository was archived by the owner on Dec 14, 2018. It is now read-only.

Content negotiation should fallback to the first formatter that can write the type #1033

Closed
yishaigalatzer opened this issue Aug 18, 2014 · 2 comments
Assignees
Milestone

Comments

@yishaigalatzer
Copy link
Contributor

example:
accept header and content type are both application/xml but the DCS serializer cannot write out the type.

The conentnegotiation system should fallback to the first formatter that can write the type.

@yishaigalatzer
Copy link
Contributor Author

@loudej this is to match content negotiation behavior in Web API, where there is a fallback to the first formatter that can write the data.

@danroth27 danroth27 added this to the 6.0.0-alpha4 milestone Aug 22, 2014
harshgMSFT added a commit that referenced this issue Aug 26, 2014
…at can write the type #1033

- Includes functional and unit tests.
harshgMSFT added a commit that referenced this issue Aug 26, 2014
…at can write the type #1033

- Includes functional and unit tests.
harshgMSFT added a commit that referenced this issue Sep 12, 2014
…at can write the type #1033

- Includes functional and unit tests.
@harshgMSFT
Copy link
Contributor

merged:
7a3dc35
dd564a3
e884a47
abf27d8
7448bf2
33173d3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants