Hy! As others pointed out, the real problem is with the url you try to use, that I skimmed over.
As Bernhard Graf wrote: "When you have 'first_name=K%E9vyn' in an URL, the meaning of %E9 is actually ambiguous, because there is no information about the encoding. Fortunately RFC 3986 advises to encode all "reserved characters" as UTF-8 before transforming them into the URI-percent encoding, because percent encoding only works with bytes (octets). In that sense, "K%E9vyn" is simply invalid, because "\xE9" alone is no valid UTF-8 encoded character. What you have there is obviously the percent encoding of the ISO-8859-1 encoding of "Kévyn". Therefore the correct RFC 3986 compliant URI-encoding for "Kévyn" would be "K%C3% A9vyn"." -- Eisenberger Tamás <[email protected]> On Sat, 2011-03-12 at 22:05 +0000, ryan lauterbach wrote: > On 12 March 2011 22:04, ryan lauterbach <[email protected]> wrote: > > 2011/3/12 Eisenberger Tamás <[email protected]>: > >> > >> This seems like some conflict between plugins, can you tell us what > >> plugins you use, with their versions... > > Everything updated yesterday. > > _______________________________________________ > 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/
