<HTML>
<HEAD>
<TITLE>Re: [OpenID] openid error mode</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>I believe that RPs in general will not be able to automatically recover from errors (other than to tell the user that something bad happened), so any error that’s returned will need to be manually interpreted by the RP’s developer.<BR>
<BR>
I would like to to see errors returned using standard error codes (machine readable) along with an URL or string for the owner of the RP to manually troubleshoot the problem. The string/url should not be displayed to the end user. This sounds like a very reasonable feature to include in OpenID v.Next.<BR>
<BR>
Allen<BR>
<BR>
<BR>
On 1/6/10 10:04 AM, "Breno de Medeiros" <<a href="breno@google.com">breno@google.com</a>> wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
I think for developers it would be much more useful to have test OPs that provide detailed error logs (e.g., entire exception stack trace, which production OPs often do not provide), so RP developers can use that for debugging.<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>