[EMAIL PROTECTED] wrote: >> That's what uri_for is already doing (I forgot to mention I'd checked >> already). >> >> uri_for: >> >> http://myserver.com/blah/?username=first.last%2Bme%40gmail.com >> >> URI::Escape: >> >> perl -MURI::Escape -e "print uri_escape('[EMAIL PROTECTED]')"; >> >> first.last%2Bme%40gmail.com >> >> Same either way. > > > perl -MURI::Escape -e "print uri_unescape('first.last%2Bme%40gmail.com');" > [EMAIL PROTECTED] > > Looks like it is a problem with the debug printing code or the some > unescape code somewhere. That is the proper escape for +.
Yes. and the problem is Catalyst is unescaping it to early, so its seeing it as a literal +, which then gets converted to a space according to the HTTP RFC. It shouldn't. There is a bug in the catalyst param handling somewhere I suspect. _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/
