use strict;
use warnings;
+use Scalar::Util qw/blessed/;
use base qw/Catalyst::Request Class::Accessor::Fast/;
+
+use Catalyst::Utils;
use HTTP::Headers::Util qw(split_header_words);
+sub _insert_self_into {
+ my ($class, $app_class ) = @_;
+ # the fallback to $app_class is for the (rare and deprecated) case when
+ # people are defining actions in MyApp.pm instead of in a controller.
+ my $app = (blessed($app_class) && $app_class->can('_application'))
+ ? $app_class->_application : Catalyst::Utils::class2appclass( $app_class ) || $app_class;
+
+ my $req_class = $app->request_class;
+ return if $req_class->isa($class);
+ if ($req_class eq 'Catalyst::Request') {
+ $app->request_class($class);
+ } else {
+ die "$app has a custom request class $req_class, "
+ . "which is not a $class; see Catalyst::Request::REST";
+ }
+}
=head1 NAME
the request object to faciliate writing REST-y code. Currently, these
methods are all related to the content types accepted by the client.
+Note that if you have a custom request class in your application, and it does
+not inherit from C<Catalyst::Request::REST>, your application will fail with an
+error indicating a conflict the first time it tries to use
+C<Catalyst::Request::REST>'s functionality. To fix this error, make sure your
+custom request class inherits from C<Catalyst::Request::REST>.
=head1 METHODS
__PACKAGE__->mk_accessors(qw(data accept_only));
-=over 4
+=over 4
=item accepted_content_types
my ( $type, $qvalue ) = @{$pair}[ 0, 3 ];
next if $types{$type};
+ # cope with invalid (missing required q parameter) header like:
+ # application/json; charset="utf-8"
+ # http://tools.ietf.org/html/rfc2616#section-14.1
+ unless ( defined $pair->[2] && lc $pair->[2] eq 'q' ) {
+ $qvalue = undef;
+ }
+
unless ( defined $qvalue ) {
$qvalue = 1 - ( ++$counter / 1000 );
}