One more XRDS and Confirm website problem

We have so problems to have a website confirm by Yahoo.
We are using Janrain library.

Website URL : www.modepass.com

  HTTP/1.1 200 OK
Date: Fri, 03 Jul 2009 09:53:17 GMT
Server: Apache/2.2.3 (Linux/SUSE)
X-Powered-By: PHP/5.2.6
X-XRDS-Location: http://www.modepass.com/xrds.xrdf
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=utf-8

XRDS : www.modepass.com/xrds.xrdf
  HTTP/1.1 200 OK
Date: Fri, 03 Jul 2009 09:54:59 GMT
Server: Apache/2.2.3 (Linux/SUSE)
Last-Modified: Thu, 02 Jul 2009 20:14:18 GMT
ETag: "2ae"
Accept-Ranges: bytes
Content-Length: 686
Vary: Accept-Encoding
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: application/xrds+xml
Length: 686 [application/xrds+xml]

The login page : www.modepass.com/join_form_new.php
and the return page : www.modepass.com/oid_return.php

This working graet with Google, Facebook and some others...
We have follow the Yahoo FAQ (http://developer.yahoo.com/openid/faq.html) and the links provided in some answers but we can't find the solution...
If we can have some help smile.gif

1 Reply
  • Hi,

    The file returned from http://www.modepass.com/
    is beyond our size limit for realm verification. We don't fetch
    large files to prevent our servers from spending too much time
    on realm verification thus to reduce the risk of denial of
    service attack. If you cannot truncate the file or set a different
    openid.realm that can return a smaller file, then you may consider
    returning the XRDS document directly if the request has the
    "Accept: application/xrds+xml,..." header. That signifies
    that it is not an ordinary request from end user' browser, but
    a request for XRDS document from the OP.

    We support this as the third option as described here:

    Yu Wang
    Yahoo! Membership team

Recent Posts

in OpenID General Discussion