failing php consumer

[artemy tregoubenko]

I found the core of the problem, some good old traffic sniffing helped me.

It's php-yadis' fault. It does only one page request, passing this request header:
Accept: application/xrds+xml
See: no alternatives, xrds only. My apache rightfully answers with:
HTTP/1.1 406 Not Acceptable
and naturally yadis can't find any openid there

Python's yadis is more flexible: it does request application/xrds+xml, but agrees to get alternatives too:
Accept: text/html; q=0.3, application/xhtml+xml; q=0.5, application/xrds+xml
That's why it keeps working, and working, and working...

I'm not sure if "not to accept html when doing yadis discovery" is question of principle for developers. If so, library should ask for plain html after yadis failed. If not, there's one-line patch for Auth_Yadis_Yadis.

Which way should I go from here?

> Hello,
>
> I've run into problems with PHP consumer. Both example installation (http://openidenabled.com/php-openid/trunk/examples/consumer/) and my installation (http://mirtesen.ru/) do not accept my openid (http://arty.name/) at all. However another example at http://www.openidenabled.com/resources/openid-test/checkup does accept my openid with yadis and without yadis.
>
> This is not caused by php multibyte parsing problems, as it happens even when I remove all non-ascii chars from my page.
>
> Any ideas?
>



-- 
arty ( http://arty.name )