Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: 3.1 M1
    • Fix Version/s: 3.2 M2
    • Component/s: Web
    • Last commented by a User:
      false

      Description

      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 SPR-7517). Furthermore, it's not possible to combine all options in the request mapping of a single method (see SPR-6497, SPR-7722).

      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.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Rossen Stoyanchev
              Reporter:
              Rossen Stoyanchev
              Last updater:
              Rossen Stoyanchev
            • Votes:
              6 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                2 years, 46 weeks, 1 day ago

                Time Tracking

                Estimated:
                Original Estimate - 0.25d
                0.25d
                Remaining:
                Remaining Estimate - 0.25d
                0.25d
                Logged:
                Time Spent - Not Specified
                Not Specified