AOL XRDS?

81 views
Skip to first unread message

ifile.it

unread,
Nov 13, 2011, 3:34:59 PM11/13/11
to google-iden...@googlegroups.com
regarding "you need to put an XRDS file in your server root to avoid the warning "Warning! site verification could not be completed" on the AOL login page"


what is the filename for this file? what content should go into it? what will be the required URL for it something like http://example.com/aol.xrds?


BTW very happy with GIT, after integrating for the day and almost ready to roll it out to replace our old legacy login/signup for our users (200,000 google analytics visits a day) just waiting to add/test AOL support

oh and Facebook/Twitter IDPs would be great!

Jin Liu

unread,
Nov 13, 2011, 9:38:30 PM11/13/11
to google-iden...@googlegroups.com
Hi,

The XRDS file could be of any name on your site, and your site could
return the file name through
1. An HTML document with a <head> element that includes a <meta>
element with http-equiv attribute, X-XRDS-Location,
- or -
2. HTTP response-headers that include an X-XRDS-Location response-header

For an example of the second approach, you can point your browser to
the GITkit demo site https://account-chooser.appspot.com/ and the XRDS
is specified in the response header "X-XRDS-Location:
https://account-chooser.appspot.com/yadis.jsp".

For the content of the XRDS file for AOL verification, you can also
refer to the demo above
(https://account-chooser.appspot.com/yadis.jsp), replacing
"https://account-chooser.appspot.com/callback" with your callback URL.

Glad to hear that you enjoy GITkit - could you let us know your site URL?

Thanks,
Jin

ifile.it

unread,
Nov 14, 2011, 7:43:09 AM11/14/11
to google-iden...@googlegroups.com
Thank you very much @Jin
It works now!

The website is http://ifile.it/
The GIT login has gone live now for all users and so far no issues and everything is going smooth.

I have some feedback for GIT developers if I may, the whole jquery UI bit while nice adds 3extra javascript calls + 60KB more to download (up from 90KB before for my site) and whats worse not all of GITkit stuff seems to be cached properly, google servers send 200 instead of 304 hence stuff doesnt get cached on users browsers, this increases page load time which i will keep an eye on with google analytics

will also see if the rate of people using the site as registered users increases, that was the reason for spending time on this, reduce login friction and get more registered users

Cheers!
Reply all
Reply to author
Forward
0 new messages