Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content negotiation improvements [SPR-8410] #13057

Closed
spring-issuemaster opened this issue Jun 7, 2011 · 0 comments
Assignees
Milestone

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Jun 7, 2011

Rossen Stoyanchev opened SPR-8410 and commented

The ContentNegotiatingViewResolver provides a range of options for configuring content negotiation based on the 'Accept' header, by path extension, or by request parameter. However when writing to the response via @ResponseBody only the 'Accept' header is used (see #12175). Furthermore, it's not possible to combine all options in the request mapping of a single method (see #11163, #12378).

This is an umbrella ticket to improve how content negotiation options are configured and to equalize the choices throughout request mappings, @ResponseBody methods, and ContentNegotiatingViewResolver.


Affects: 3.1 M1

Sub-tasks:

  • #12288 Allow valid file extension paths for content negotiation to be specified
  • #13064 Introduce ContentNegotiationStrategy abstraction
  • #13065 Enhance "produces" condition to use the new ContentNegotiationManager type
  • #13066 Enhance RequestResponseBodyMethodProcessor and HttpEntityMethodProcessor to use new the ContentNegotiationManager type
  • #13067 Enhance ContentNegotiatingViewResolver to use the new ContentNegotiationManager type
  • #13068 Update the MVC Java config and the MVC namespace to support content negotiation options
  • #13120 Configure PatternsRequestCondition with information that allows it to do a smart suffix pattern match

Issue Links:

  • #13190 Spring MVC - Ability to use a Converter based on the Path Extension instead of Accep Header. ("is duplicated by")
  • #13282 Allow customization of ContentNegotiatingViewResolver by making some of its methods protected
  • #13791 Add extension element to Spring Web MVC @RequestMapping annotation
  • #11658 Add content-negotiation to RequestBody and ResponseBody processing ("supersedes")
  • #11163 @RequestMapping should support accept header and url extension ("supersedes")
  • #12378 @RequestMapping should support alternative between a header and a url extension ("supersedes")
  • #12175 Introduce request parameter based content negotiation for ResponseBody / HttpMessageConverter approach ("supersedes")

6 votes, 9 watchers

@spring-issuemaster spring-issuemaster added this to the 3.2 M2 milestone Jan 11, 2019
This was referenced Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.