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

Incoming content negotiation based on content-type #107

Closed
pranavkm opened this issue Mar 18, 2014 · 2 comments
Closed

Incoming content negotiation based on content-type #107

pranavkm opened this issue Mar 18, 2014 · 2 comments
Assignees
Milestone

Comments

@pranavkm
Copy link
Contributor

Right now individual formatters look at a list of content types and decide if they support the request. We need to figure out what a proper pattern for this needs to be.

@JaneZhouQ JaneZhouQ added this to the Post Alpha milestone May 14, 2014
@yishaigalatzer yishaigalatzer removed this from the Post Alpha milestone May 23, 2014
@danroth27 danroth27 added this to the 1.0.0-alpha2 milestone May 29, 2014
@danroth27 danroth27 changed the title Determine how we can do formatter selection from content-type Incoming content negotiation based on content-type May 29, 2014
@danroth27 danroth27 modified the milestones: 6.0.0-alpha3, 1.0.0-alpha3 Jul 7, 2014
@harshgMSFT
Copy link
Contributor

Workitems:

  1. Provide a collection of Input formatters: The defaults will be exposed through MVCOptions.XmlInputFormatter should be chosen based on MvcOptions. #851 -1 day.
  2. Changing the current api structure to use the httpabstraction header parsing and use that for content type matching. - 1 day.
  3. Need to design around how to return an exception back. Content Negotiation need to return 400 Bad Request \ 415 unsupported media type  #458 - 3 days
   Where do the input formatters hang off ( it is helpful if someone wants to use a filter to add/overide the default formatters). 

@danroth27 danroth27 modified the milestones: 6.0.0-alpha3, 6.0.0-alpha4 Aug 12, 2014
@harshgMSFT
Copy link
Contributor

Closing this one as the items are being tracked separately.

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

5 participants