Bug #69062 for Catalyst-Action-REST: Docs say params come in via $c->req->data. Actually, they come in via $c->req->params.

Thu Jun 23 19:00:58 2011 quinn [...] fairpath.com - Ticket created

Subject:

Docs say params come in via $c->req->data. Actually, they come in via $c->req->params.

The subject line pretty much says it all. Whether by GET or by POST, $c->req->data is always undef, and $c->req->params always contains the request parameters. I can provide sample code to reproduce the problem, plus a patch, but first I want to make sure someone is actually monitoring this queue. Please respond. Thanks!

Mon Aug 01 14:27:28 2011 rjk [...] tamias.net - Correspondence added

From:

rjk [...] tamias.net

I think you are misunderstanding the documentation. The HTTP POST, PUT, and OPTIONS methods will all automatically deserialize the contents of $c->request->body into the $c->request->data hashref, based on the request's Content-type header. $c->req->data contains the deserialized *body* of the request. Request parameters are, and should be, in $c->req->params.

Mon Aug 01 14:27:34 2011 The RT System itself - Status changed from 'new' to 'open'

Mon Aug 01 15:35:57 2011 quinn [...] fairpath.com - Correspondence added

On Mon Aug 01 14:27:28 2011, rjk-cpan@tamias.net wrote: Show quoted text

> I think you are misunderstanding the documentation. > > The HTTP POST, PUT, and OPTIONS methods will all automatically > deserialize the contents of $c->request->body into the > $c->request->data hashref, based on the request's Content-type > header. > > $c->req->data contains the deserialized *body* of the request. Request > parameters are, and should be, in $c->req->params.

You're right: I was misunderstanding the documentation. Thanks for clarifying. Given what you said, the module works as expected.

Mon Aug 01 15:46:01 2011 bobtfish [...] bobtfish.net - Status changed from 'open' to 'resolved'