Issue 47: Problem with diacrirics
Status:  Invalid
Owner: ----
Closed:  Sep 2011
Reported by mho...@gmail.com, Sep 10, 2011
If some openid fields contains diacritics e.g. ščťžýáň validation fails

Tested with myopenid.com provider.

Sep 11, 2011
Project Member #1 mewp...@gmail.com
It works for me. I've set my full name to "ščťžýáň" at myopenid.com, then tried to get that attribute and succeeded at it.

Please provide more information.
Sep 12, 2011
#2 mho...@gmail.com
Libopenid version - 0.5
I tried to login to example.php
with 
       	    $openid->required = array(
                'namePerson/friendly',
                'contact/email',
                'namePerson',
                'person/gender',
                'contact/country/home',
                'pref/language',
                'pref/timezone',
                );
if I comment out any item, validation works.

The problem may be(and probably is) on the myopenid.com
Sep 12, 2011
Project Member #3 mewp...@gmail.com
Like I said, I have tested it with myopenid and it works.

However, you said any item? That is, the following two examples work?

 $openid->required = array(
                'namePerson/friendly',
                'contact/email',
                'namePerson',
//              'person/gender',
                'contact/country/home',
                'pref/language',
                'pref/timezone',
                );

 $openid->required = array(
                'namePerson/friendly',
                'contact/email',
                'namePerson',
                'person/gender',
//              'contact/country/home',
                'pref/language',
                'pref/timezone',
                );

If that's the case, it seems rather strange.
Sep 12, 2011
#5 mho...@gmail.com
both work for me.
if no item is comented out, it fails.
I'm using this account for testing
test47.myopenid.com pass:test47
Sep 15, 2011
Project Member #6 mewp...@gmail.com
After testing, it seems that myopenid sometimes sends improperly encoded data. Not much I can do about it, though.

Explanation how this happens:
myopenid tries to follow a suggestion in the spec that large requests should be sent as POST. However, in order to make a POST request from the users' browser, it makes a form that automatically submits itself, and this form improperly encodes the sent data.

So, it's a bug in myopenid. Thanks for reporting it anyway.
Status: Invalid