This is already supported. Look at Request::getContent().

That's not the same thing. You can't bind a form to a request submitted via PUT unless the PUT request values are actually part of the Request::request ParameterBag.

This cannot be applied since php://input can only be read once. People would have no way to access the PUT data anymore. Besides the put data might not be a url-encoded list of key/value pairs.

If you need this then it's better if you do that in a Request listener.

OK, the read-once thing is certainly a deal breaker. But there must be a way to implement this in the Request class as standard. Symfony 1 supported PUT requests without a problem.

I flattened the two commits. The pull no longer causes the Request have no value for getContent().

You probably also want to check if the content type is 'application/x-www-form-urlencoded' (or null?). As Johannes suggested, this should probably go in a RequestListener.

Kind of like is done in the RestBundle: https://github.com/FriendsOfSymfony/RestBundle/blob/master/Request/RequestListener.php except it will be in the FrameworkBundle.

I wasn't aware of the existence of RestBundle. I'm going to investigate that before pursuing this further.

Thanks for the pointer.

@Chekote: is there anything missing in RestBundle for your use case?

Not sure yet. I'm going to be trying it out today (or Tomorrow, Monday's are
hectic).

On Mon, May 9, 2011 at 7:38 AM, lsmith77 <
reply@reply.github.com>wrote:

@Chekote: is there anything missing in RestBundle for your use case?

Reply to this email directly or view it on GitHub:
#793 (comment)

I've just create a patch in the Form component here #849