Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

acme (189)

acme
  (email not shown publicly)
http://www.astray.com/

Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

Journal of acme (189)

Saturday May 03, 2008
01:30 PM

Help needed: Test::WWW::Mechanize::Catalyst

[ #36321 ]
I really like my Test::WWW::Mechanize::Catalyst module. Well, I don't like how it's such a hack internally for something which should be so simple. However, I need some help: the recent releases of libwww-perl break the tests and I can't figure out how to fix it. Could you help?
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Have you tried the latest version? Looks like some changes have happened in the problem area, maybe they have sorted it out.
  • decoded_content normally returns a TEXT string, whereas content only supports OCTET strings. When LWP got fixed, your module got broken. Or, well, its error was exposed.

    Using doceded_content is fine, but don't try to stuff its text result back into the byte content container. If you're using decoded_content but don't really care about character sets, supply charset => 'none' and continue using it as you are now.

    See also the PM thread at http://perlmonks.org/?node_id=683833 [perlmonks.org] and dngor's solution at http:// [p3m.org]