On 23 Nov 2010, at 16:22, Ronald J Kimball wrote:
Why? Where is the code which forces it to be a POST?
In Catalyst::Action::Deserialize:
sub execute {
my $self = shift;
my ( $controller, $c ) = @_;
my @demethods = qw(POST PUT OPTIONS DELETE);
Dang, my bad.
Cheers
t0m
On Mon, Nov 22, 2010 at 7:33 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 22 Nov 2010, at 18:28, Ronald J Kimball wrote:
It doesn't care what the request method is, as long as it's POST, PUT,
OPTIONS, or DELETE. ;)
No, it just doesn't care.
If I create
On 22 Nov 2010, at 17:44, Ronald J Kimball wrote:
This works for JSON requests (e.g. application/json), but not for
JSONP requests (e.g. text/javascript), because there is no
Catalyst::Action::Deserialize::JSONP. I guess I could create one that
extends Catalyst::Action::Deserialize::JSON...
On Mon, Nov 22, 2010 at 12:53 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 22 Nov 2010, at 17:44, Ronald J Kimball wrote:
This works for JSON requests (e.g. application/json), but not for
JSONP requests (e.g. text/javascript), because there is no
Catalyst::Action::Deserialize::JSONP. I
On 22 Nov 2010, at 18:28, Ronald J Kimball wrote:
It doesn't care what the request method is, as long as it's POST, PUT,
OPTIONS, or DELETE. ;)
No, it just doesn't care.
If I create Catalyst::Action::Deserialize::JSONP, I'll still need to
convert the GET request to a POST. That seems to
