Hy!

Yes using encode_utf8 makes the test works.

But anyway, this looks like a problem with the test, because we have
tests to compare the entire captures / arguments / params strings with
their originals, and if these tests pass the length of the strings must
be ok!

So Erik, can you please review your test, or explain a real word
situation of the problem you facing?

I actually use utf8 strings in url's now without problems :)
-- 
Eisenberger Tamás <ta...@eisenberger.hu>

On Thu, 2011-03-03 at 21:33 -0800, Bill Moseley wrote:
> Does this help?
> 
> On Thu, Mar 3, 2011 at 2:38 PM, Erik Wasser <erik.was...@iquer.net>
> wrote:
>         foreach my $u ('http://localhost/test/%E3%81%8B',
>         "http://localhost/test/\x{304b}"; )
>         {
>            my $request = HTTP::Request->new(
>                'GET'=> encode_utf8($u), [ 'Content-Type' =>
>         'text/html; charset=utf8', ],
>            );
>            print $request->as_string();
>            my $response = request( $request );
>            is( $response->content, 'length = 1', 'length = 1' );
>         }
>         
> 
> -- 
> Bill Moseley
> mose...@hank.org
> _______________________________________________
> List: Catalyst@lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

Reply via email to