Sorry, you wrote that C::P::U::E fails to decode utf8, but not that it's already decoded and your app fails..
This seems like some conflict between plugins, can you tell us what plugins you use, with their versions, catalyst's version and the order of plugins loaded? The order does matter in case of C::P::U::E because it should be the first getting the input! -- Eisenberger Tamás <[email protected]> On Sat, 2011-03-12 at 11:32 +0000, Ryan Lauterbach wrote: > > So utf8::is_utf8 means that the string has multiple bytes in one > > character. > > > > Of course $enc->decode() fails to decode the already decoded "\xE9" > > again. > > > > You can use that string without calling decode safely. > > C::P::Unicode::Encoding will encode it before it gets written to the > > output. > > > > C::P::U::E is failing on decode straight from the url, before it gets to my > code, so this might be a bug somewhere along the pipeline. How has it been > decoded before it gets to c::p::u::e? Why is the is_UTF8 flag not set, thus > attempting to decode again? > > Basically a UTF8 URL kills my app until I remove u::e. > > Thanks > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
