This queue is for tickets about the Net-OpenID-Consumer CPAN distribution.

Report information
The Basics
Id:
41310
Status:
resolved
Priority:
Low/Low

People
Owner:
Nobody in particular
Requestors:
MART [...] cpan.org
Cc:
AdminCc:

BugTracker
Severity:
Normal
Broken in:
(no value)
Fixed in:
1.12



Subject: We only allow XRDS documents in UTF-8
MIME-Version: 1.0
X-Mailer: MIME-tools 5.426 (Entity 5.426)
Content-Type: text/plain
Charset: utf8
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 331
The application/xrds+xml MIME type accepts a "charset" attribute which indicates the default charset to use when parsing the body. Currently we ignore this and assume UTF-8. This can be worked around by putting the correct charset in the <?xml ?
Show quoted text
> prologue of the document, as long as the selected charset is ASCII-
compatible.
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-2599-1321148080-558.41310-0-0@rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 365
I believe this is fixed in Net-OpenID-Consumer 1.12 If you wish to try it out please make sure you've also installed the latest version of Net-OpenID-Common. Feel free to re-open (or start a new ticket) if it turns out I'm mistaken about this. Thanks for the report and sorry this took so long to get to... -- Roger Crew (new co-maintainer as of a few weeks ago)


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.