You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
at line 430 in openid.php we have:
if (isset($headers['content-type'])
&& (strpos($headers['content-type'], 'application/xrds+xml') !== false
|| strpos($headers['content-type'], 'text/xml') !== false)
) {
# Apparently, some providers return XRDS documents as text/html.
# While it is against the spec, allowing this here shouldn't break
# compatibility with anything.
# ---
# Found an XRDS document, now let's find the server, and optionally delegate.
$content = $this->request($url, 'GET');
I had exactly the problem, as stated in above comment, that when doing an HTTP
HEAD request the
returned mimetype 'text/html' however when doing an HTTP GET request it
returns an XRDS document with as mimetype 'application/xrds+xml'.
However it appears for me that the comment only makes sense if you change in
the if statement 'text/xml' to 'text/html'!
So I guess it is a type? At least it solved my problem: allowing also
'text/html' in the if statement so that it is going to
fetch and parse the XRDS document.
Thus I propose change line 432;
|| strpos($headers['content-type'], 'text/xml') !== false)
into:
|| strpos($headers['content-type'], 'text/html') !== false)
Best regards,
Harco Kuppens
Original issue reported on code.google.com by [email protected] on 18 Jun 2013 at 10:38
The text was updated successfully, but these errors were encountered:
I just spent a good while tracking down why openid->identity was always coming
back with https://open.login.yahooapis.com/openid20/user_profile/xrds for yahoo
long story short, the mentioned if statement was failing... and lightopenid
incorrectly updated the value for identity/claimed_id
I'm guessing the if statement is meant to check for
'application/xrds+xml' || 'text/xml' || 'text/html'
Original issue reported on code.google.com by
[email protected]
on 18 Jun 2013 at 10:38The text was updated successfully, but these errors were encountered: