- If we get a response set from $res->from_psgi_response and that response
has a charset for the content type, we clear encoding for the rest of the
response (avoid double encoding).
- -
+ - Documentation updates and typo fixes across various UTF8 docs (Mark Ellis++)
5.90079_007 - 2015-01-07
- Merged from Stable (5.90079)
__PACKAGE__->_encode_check(Encode::FB_CROAK | Encode::LEAVE_SRC);
# Remember to update this in Catalyst::Runtime as well!
-our $VERSION = '5.90079_007';
+our $VERSION = '5.90079_008';
$VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases
sub import {
return eval {
local $/;
$slurped = $fh->getline;
- $parser->can("decode_json")->($slurped);
+ $parser->can("decode_json")->($slurped); # decode_json does utf8 decoding for us
} || Catalyst::Exception->throw(sprintf "Error Parsing POST '%s', Error: %s", (defined($slurped) ? $slurped : 'undef') ,$@);
},
};
# to assume its properly encoded and NOT encode for this response. Otherwise
# We risk double encoding.
if($self->content_type_charset) {
+ # We have to do this since for backcompat reasons having a charset doesn't always
+ # mean that the body is already encoded :(
$self->_context->clear_encoding;
}
}
# Remember to update this in Catalyst as well!
-our $VERSION = '5.90079_007';
+our $VERSION = '5.90079_008';
$VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases
=head1 NAME