-
Notifications
You must be signed in to change notification settings - Fork 38.9k
Closed
Labels
in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)type: taskA general taskA general task
Milestone
Description
Rossen Stoyanchev opened SPR-8415 and commented
For "x-www-form-urlencoded" data one could use an @RequestBody (via FormHttpMessageConverter) or a @ModelAttribute method argument (via data binding). The latter has a few advantages:
- it results in a typed object rather than MultiValueMap
- with MultiValueMap you lose the ability to apply automatic validation
- use of request.getParameter*() before the
@RequestBodyargument is resolved causes problems
Affects: 3.1 M1
Issue Links:
- resolveRequestBody algorithm does not take into account ConversionService when determining if binding is possible [SPR-6729] #11395 resolveRequestBody algorithm does not take into account ConversionService when determining if binding is possible
- Support for PUTting form-encoded data [SPR-5628] #10299 Support for PUTting form-encoded data
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)type: taskA general taskA general task