in reply to Explicit charset confuses WWW::Mechanize and/or HTTP::Response

save_content never encodes the previously decoded content. Bug!
  • Comment on Re: Explicit charset confuses WWW::Mechanize and/or HTTP::Response
  • Download Code

Replies are listed 'Best First'.
Re^2: Explicit charset confuses WWW::Mechanize and/or HTTP::Response
by Anonymous Monk on May 14, 2009 at 04:05 UTC
    The bug is it should binmode unconditionally.

      No. You can't write decoded text to a file, binmoded or not.

      Or do you mean :encoding needs to be specified unconditionally? That's wrong too, since Mechanize doesn't always decode the content.