Resolve MediaType in ContentNegotiatingViewResolver Based on Request Parameter Existence [SPR-7115]

[spring-projects-issues]

Nick Padgett opened SPR-7115 and commented

There are scenarios where the content type for a request should be determined based off of the existence of a request parameter.

For example, when a user requests http://some.tld/events they might get an "application/json" response, but when they request http://some.tld/events?callback=random_method they might get an "text/javascript" response. This is the expected behavior when working with JsonP.

Here's a sample URL from Amazon. Ignore the http response code and look at the http response content types:
http://query.yahooapis.com/v1/public/yql?q=select * from social.connections where owner_guid=me&format=json
http://query.yahooapis.com/v1/public/yql?q=select * from social.connections where owner_guid=me&format=json&callback=cbfunc

More documentation:
http://developer.yahoo.com/yql/guide/response.html

---

Affects: 3.0.2

Issue Links:

• Update the MVC Java config and the MVC namespace to support content negotiation options [SPR-8420] #13068 Update the MVC Java config and the MVC namespace to support content negotiation options ("is superseded by")

2 votes, 4 watchers

[spring-projects-issues]

Brian Clozel commented

As of #13068 (and earlier?), the content negotiation can be configured with a {favorParameter}} which does just that. Closing this issue as it's been solved previously.