From: John Napiorkowski Date: Tue, 25 Nov 2014 19:22:53 +0000 (-0600) Subject: make the new encoding stuff work with ash multivalue if you want that stuff X-Git-Tag: 5.90079_001~15 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=commitdiff_plain;h=c0d561c143f688e7fb322fcf0b2e8ca64022e7d8 make the new encoding stuff work with ash multivalue if you want that stuff --- diff --git a/lib/Catalyst.pm b/lib/Catalyst.pm index eaf5079..725494c 100644 --- a/lib/Catalyst.pm +++ b/lib/Catalyst.pm @@ -2280,23 +2280,6 @@ Prepares body parameters. sub prepare_body_parameters { my $c = shift; $c->request->prepare_body_parameters( $c, @_ ); - - # If we have an encoding configured (like UTF-8) in general we expect a client - # to POST with the encoding we fufilled the request in. Otherwise don't do any - # encoding (good change wide chars could be in HTML entity style llike the old - # days -JNAP - - # so, now that HTTP::Body prepared the body params, we gotta 'walk' the structure - # and do any needed decoding. - - # This only does something if the encoding is set via the encoding param. Remember - # this is assuming the client is not bad and responds with what you provided. In - # general you can just use utf8 and get away with it. - - if($c->encoding) { - my $current_parameters = $c->request->body_parameters; - $c->request->body_parameters($c->_handle_unicode_decoding($current_parameters)); - } } =head2 $c->prepare_connection @@ -3062,6 +3045,7 @@ Sets up the input/output encoding. See L sub setup_encoding { my $c = shift; + # This is where you'd set a default encoding my $enc = delete $c->config->{encoding}; $c->encoding( $enc ) if defined $enc; } diff --git a/lib/Catalyst/Request.pm b/lib/Catalyst/Request.pm index 7b41cfe..cdaa173 100644 --- a/lib/Catalyst/Request.pm +++ b/lib/Catalyst/Request.pm @@ -312,7 +312,7 @@ sub prepare_body_chunk { } sub prepare_body_parameters { - my ( $self ) = @_; + my ( $self, $c ) = @_; $self->prepare_body if ! $self->_has_body; @@ -320,9 +320,29 @@ sub prepare_body_parameters { return $self->_use_hash_multivalue ? Hash::MultiValue->new : {}; } + my $params = $self->_body->param; + + # If we have an encoding configured (like UTF-8) in general we expect a client + # to POST with the encoding we fufilled the request in. Otherwise don't do any + # encoding (good change wide chars could be in HTML entity style llike the old + # days -JNAP + + # so, now that HTTP::Body prepared the body params, we gotta 'walk' the structure + # and do any needed decoding. + + # This only does something if the encoding is set via the encoding param. Remember + # this is assuming the client is not bad and responds with what you provided. In + # general you can just use utf8 and get away with it. + # + # I need to see if $c is here since this also doubles as a builder for the object :( + + if($c and $c->encoding) { + $params = $c->_handle_unicode_decoding($params); + } + return $self->_use_hash_multivalue ? - Hash::MultiValue->from_mixed($self->_body->param) : - $self->_body->param; + Hash::MultiValue->from_mixed($params) : + $params; } sub prepare_connection {