<html>
<body>
<blockquote type=cite class=cite cite=""><font size=3> If the
response includes both a content-type response-header specifying MIME
media type, application/xrds+xml and a Yadis Resource Descriptor URL,
then the Yadis document is located by that Yadis Resource Descriptor
URL.<br><br>
But, if such case, access become eternal loop.<br><br>
Accessing URL :
<a href="http://id.example.com/" eudora="autourl">
http://id.example.com/</a><br>
Content-type header: application/xrds+xml<br>
X-XRDS-Location:
<a href="http://id.example.com/" eudora="autourl">
http://id.example.com/</a></font></blockquote><br>
<font size=3>Ohtsuka-san:<br><br>
</font>The case where both a <font size=3>Content-Type response-header
and an X-XRDS-Location response-header are returned means the XRDS
document located by this URL is not the Yadis document. That means
the Yadis is somewhere else. The X-XRDS-Location response-header
should locate it for you.<br><br>
Of course, this loop can occur without a Content-Type response-header
being returned. You better stay out of the loop in every
case.<br><br>
The site you describe does not conform to the Yadis Protocol. This
is a failure.<br><br>
Cordially, Joaquin<br>
</font></body>
</html>