X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst.pm;h=7f9fe309f55c4999f376a7f5f5508ec099ebf4a1;hp=1808a4dcf6e0df3330d53d27aa3da40afe16d7e7;hb=a050c28ac1ca3424009799a5472886323b8250bf;hpb=de2e9a6f5290e2f0b0971ce995ae65afc1cacf0a diff --git a/lib/Catalyst.pm b/lib/Catalyst.pm index 1808a4d..7f9fe30 100644 --- a/lib/Catalyst.pm +++ b/lib/Catalyst.pm @@ -204,7 +204,7 @@ sub composed_stats_class { __PACKAGE__->_encode_check(Encode::FB_CROAK | Encode::LEAVE_SRC); # Remember to update this in Catalyst::Runtime as well! -our $VERSION = '5.90110'; +our $VERSION = '5.90112'; $VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases sub import { @@ -3571,18 +3571,23 @@ sub setup_encoding { =head2 handle_unicode_encoding_exception -Hook to let you customize how encoding errors are handled. By default +Hook to let you customize how encoding errors are handled. By default we just throw an exception and the default error page will pick it up. -Receives a hashref of debug information. Example of call: +Receives a hashref of debug information. Example of call (from the +Catalyst internals): - $c->handle_unicode_encoding_exception({ + my $decoded_after_fail = $c->handle_unicode_encoding_exception({ param_value => $value, error_msg => $_, encoding_step => 'params', - }); + }); + +The calling code expects to receive a decoded string or an exception. -You can override this for custom handling of unicode errors. If you want a -custom response here, one approach is to throw an HTTP style exception: +You can override this for custom handling of unicode errors. By +default we just die. If you want a custom response here, one approach +is to throw an HTTP style exception, instead of returning a decoded +string or throwing a generic exception. sub handle_unicode_encoding_exception { my ($c, $params) = @_; @@ -3595,13 +3600,15 @@ in your application: sub handle_unicode_encoding_exception { my ($c, $params) = @_; $c->stash(BAD_UNICODE_DATA=>$params); + # return a dummy string. return 1; } -NOTE: Please keep in mind that once an error like this occurs, the request -setup is aborted, which means the state of C<$c> and related context parts like -the request and response may not be setup up correctly (since we never finished the -setup. +NOTE: Please keep in mind that once an error like this occurs, +the request setup is still ongoing, which means the state of C<$c> and +related context parts like the request and response may not be setup +up correctly (since we haven't finished the setup yet). If you throw +an exception the setup is aborted. =cut