How can I avoid encoding errors using Net::OpenID::Consumer with Yahoo OpenIDs?
I've written a Dancer web app that utilizes Net::OpenID::Consumer to consume OpenIDs for authentication.  It works well with Google and MyOpenID, but not Yahoo.  When a user tries to authenticate using their Yahoo account, HTML::Parser warns "Parsing of undecoded UTF-8 will give garbage when decoding entities" and this warning kills my app (rightfully so).

I don't see any existing bugs with Net::OpenID::Consumer (or Common) that relate to this.  The HTTP headers and the HTML meta tags both specify UTF-8 for the 'claimed id' URI.  Why would the response not be decoded for HTML::Parser?  Am I missing something obvious?
How can I avoid encoding errors using Net::OpenID::Consumer with Yahoo OpenIDs?
===

I've written a Dancer web app that utilizes Net::OpenID::Consumer to consume OpenIDs for authentication.  It works well with Google and MyOpenID, but not Yahoo.  When a user tries to authenticate using their Yahoo account, HTML::Parser warns "Parsing of undecoded UTF-8 will give garbage when decoding entities" and this warning kills my app (rightfully so).

I don't see any existing bugs with Net::OpenID::Consumer (or Common) that relate to this.  The HTTP headers and the HTML meta tags both specify UTF-8 for the 'claimed id' URI.  Why would the response not be decoded for HTML::Parser?  Am I missing something obvious?