Bug #36913

HTTP PUT data not regonized as arguments

Added by Pankaj Lele about 3 years ago. Updated about 3 years ago.

Status:Resolved Start date:2012-05-07
Priority:Must have Due date:
Assigned To:Robert Lemke % Done:

100%

Category:Http
Target version:TYPO3 Flow Base Distribution - 1.1 beta 2
PHP Version:5.3 Complexity:medium
Has patch:No Affected Flow version:FLOW3 1.1.0 beta 1

Description

Data submitted with HTTP PUT method is not recognized in the TYPO3\FLOW3\Http\Request

This is required while developing a REST service with FLOW3. So e.g. with curl call like:

curl -X PUT -d "name=New name" http://myservice.com/users/12345

the MyController->updateAction($user, $name) would receive $name as an argument.


Related issues

related to TYPO3.Flow - Bug #37445: Router overrides POST arguments Resolved 2012-05-23
related to TYPO3.Flow - Feature #37402: Make request handling RESTfuller Resolved 2012-05-22

Associated revisions

Revision 26f83dd3
Added by Robert Lemke about 3 years ago

[FEATURE] Support for HTTP PUT/DELETE arguments

This adds transparent argument support for arguments
in PUT and DELETE requests which are passed through
the request body. Depending on the content type of
the request, the message body is parsed and then
mapped into arguments for further use in controllers.

The following content content types are currently
supported:

  • application/x-www-form-urlencoded
  • application/json
  • xml

Change-Id: Ifa6712e38d68c94cd9ec79a499d25ee577fc2d57
Resolves: #36913
Related: #37402
Related: #33371
Releases: 1.1, 1.2

Revision 8ce2f8da
Added by Robert Lemke about 3 years ago

[FEATURE] Support for HTTP PUT/DELETE arguments

This adds transparent argument support for arguments
in PUT and DELETE requests which are passed through
the request body. Depending on the content type of
the request, the message body is parsed and then
mapped into arguments for further use in controllers.

The following content content types are currently
supported:

  • application/x-www-form-urlencoded
  • application/json
  • xml

Change-Id: Id938025a7359b6ec3b29cec5fd7259db97703a16
Resolves: #36913
Related: #37402
Related: #33371
Releases: 1.1, 1.2

History

#1 Updated by Robert Lemke about 3 years ago

  • Status changed from New to Accepted
  • Priority changed from Should have to Must have
  • Target version changed from 1.1 to 1.1 beta 2
  • Complexity set to medium
  • Affected Flow version changed from Git master to FLOW3 1.1.0 beta 1

#2 Updated by Gerrit Code Review about 3 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11531

#3 Updated by Gerrit Code Review about 3 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11531

#4 Updated by Gerrit Code Review about 3 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/11531

#5 Updated by Gerrit Code Review about 3 years ago

Patch set 1 for branch FLOW3-1.1 has been pushed to the review server.
It is available at http://review.typo3.org/11546

#6 Updated by Gerrit Code Review about 3 years ago

Patch set 2 for branch FLOW3-1.1 has been pushed to the review server.
It is available at http://review.typo3.org/11546

#7 Updated by Robert Lemke about 3 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF