<remark>Further updated to track XMPP WG output; fixed several errors.</remark>
</revision>
<revision>
<version>0.2</version>
<date>2003-08-13</date>
<initials>psa</initials>
<remark>Updated to track XMPP WG output.</remark>
</revision>
<revision>
<version>0.1</version>
<date>2003-05-21</date>
<initials>rn</initials>
<remark>Initial release.</remark>
</revision>
</header>
<section1topic='Introduction'>
<p>&xmppcore; documents formats and semantics for stanza error responses. The XML of these errors is different from that of errors that have been traditionally used on the Jabber network.</p>
<p>Until such time that all entities support these new XMPP-style errors, there is a need for entities to issue errors that are understandable by both legacy and XMPP-compliant entities. This document outlines an appropriate mapping to allow this to occur.</p>
<p>This document can also be used by implementers of legacy protocols to determine which XMPP-style error should be used when only a legacy error code is documented.</p>
</section1>
<section1topic='Supporting Legacy Entities'>
<p>XMPP-compliant entities can issue errors to legacy clients and servers by adding a "code" attribute to the <error/> element it sends.</p>
<p>Legacy entities receiving this error will use the "404" to determine what happened, while XMPP-compliant entities will use the error type and the child element that specifies the condition.</p>
<p>XMPP-compliant entities should add the following error codes to errors if they want them to be understood by legacy entities:</p>
<tablecaption='Error codes to add to XMPP-style errors'>
<tr>
<th>XMPP error condition</th>
<th>XMPP error type</th>
<th>Legacy error code</th>
</tr>
<tr>
<td><bad-request/></td>
<td>modify</td>
<td>400</td>
</tr>
<tr>
<td><conflict/></td>
<td>cancel</td>
<td>409</td>
</tr>
<tr>
<td><feature-not-implemented/></td>
<td>cancel</td>
<td>501</td>
</tr>
<tr>
<td><forbidden/></td>
<td>auth</td>
<td>403</td>
</tr>
<tr>
<td><gone/></td>
<td>modify</td>
<td>302 (permanent)</td>
</tr>
<tr>
<td><internal-server-error/></td>
<td>wait</td>
<td>500</td>
</tr>
<tr>
<td><item-not-found/></td>
<td>cancel</td>
<td>404</td>
</tr>
<tr>
<td><jid-malformed/></td>
<td>modify</td>
<td>400</td>
</tr>
<tr>
<td><not-acceptable/></td>
<td>modify</td>
<td>406</td>
</tr>
<tr>
<td><not-allowed/></td>
<td>cancel</td>
<td>405</td>
</tr>
<tr>
<td><not-authorized/></td>
<td>auth</td>
<td>401</td>
</tr>
<tr>
<td><payment-required/></td>
<td>auth</td>
<td>402</td>
</tr>
<tr>
<td><recipient-unavailable/></td>
<td>wait</td>
<td>404</td>
</tr>
<tr>
<td><redirect/></td>
<td>modify</td>
<td>302 (temporary)</td>
</tr>
<tr>
<td><registration-required/></td>
<td>auth</td>
<td>407</td>
</tr>
<tr>
<td><remote-server-not-found/></td>
<td>cancel</td>
<td>404</td>
</tr>
<tr>
<td><remote-server-timeout/></td>
<td>wait</td>
<td>504</td>
</tr>
<tr>
<td><resource-constraint/></td>
<td>wait</td>
<td>500</td>
</tr>
<tr>
<td><service-unavailable/></td>
<td>cancel</td>
<td>503</td>
</tr>
<tr>
<td><subscription-required/></td>
<td>auth</td>
<td>407</td>
</tr>
<tr>
<td><undefined-condition/></td>
<td>[any]</td>
<td>500</td>
</tr>
<tr>
<td><unexpected-request/></td>
<td>wait</td>
<td>400</td>
</tr>
</table>
</section1>
<section1topic='Implementing Legacy Protocols'>
<p>Implementors of legacy protocols should use the appropriate XMPP-style error alongside a legacy error code as specified in the following table:</p>
<tablecaption='Mapping of legacy error codes to XMPP-style errors'>
<tr>
<th>Legacy error code</th>
<th>Meaning</th>
<th>XMPP error condition</th>
<th>XMPP error type</th>
</tr>
<tr>
<td>302</td>
<td>Redirect</td>
<td><redirect/> (temporary) or <gone/> (permanent)</td>
<td>modify</td>
</tr>
<tr>
<td>400</td>
<td>Bad Request</td>
<td><bad-request/>
<note>See also the <jid-malformed/> and <unexpected-request/> stanza errors.</note>
</td>
<td>modify</td>
</tr>
<tr>
<td>401</td>
<td>Not Authorized</td>
<td><not-authorized/>
<note>See also the <not-authorized/> stream error.</note>
</td>
<td>auth</td>
</tr>
<tr>
<td>402</td>
<td>Payment Required</td>
<td><payment-required/></td>
<td>auth</td>
</tr>
<tr>
<td>403</td>
<td>Forbidden</td>
<td><forbidden/></td>
<td>auth</td>
</tr>
<tr>
<td>404</td>
<td>Not Found</td>
<td><item-not-found/>
<note>See also the <remote-server-not-found/> stanza error.</note>
</td>
<td>cancel</td>
</tr>
<tr>
<td>405</td>
<td>Not Allowed</td>
<td><not-allowed/></td>
<td>cancel</td>
</tr>
<tr>
<td>406</td>
<td>Not Acceptable</td>
<td><not-acceptable/>
<note>See also the <unexpected-request/> stanza error.</note>
</td>
<td>modify</td>
</tr>
<tr>
<td>407</td>
<td>Registration Required</td>
<td><registration-required/></td>
<td>auth</td>
</tr>
<tr>
<td>408</td>
<td>Request Timeout</td>
<td><remote-server-timeout/></td>
<td>wait</td>
</tr>
<tr>
<td>409</td>
<td>Conflict</td>
<td><conflict/></td>
<td>cancel</td>
</tr>
<tr>
<td>500</td>
<td>Internal Server Error</td>
<td><internal-server-error/>
<note>See also the <undefined-condition/> stanza error.</note>
</td>
<td>wait</td>
</tr>
<tr>
<td>501</td>
<td>Not Implemented</td>
<td><feature-not-implemented/></td>
<td>cancel</td>
</tr>
<tr>
<td>502</td>
<td>Remote Server Error</td>
<td><service-unavailable/></td>
<td>wait</td>
</tr>
<tr>
<td>503</td>
<td>Service Unavailable</td>
<td><service-unavailable/></td>
<td>cancel</td>
</tr>
<tr>
<td>504</td>
<td>Remote Server Timeout</td>
<td><remote-server-timeout/></td>
<td>wait</td>
</tr>
<tr>
<td>510</td>
<td>Disconnected</td>
<td><service-unavailable/></td>
<td>cancel</td>
</tr>
</table>
</section1>
<section1topic='Conclusion'>
<p>Mapping legacy error codes to XMPP-style errors is an inexact science, and there are likely to be inconsistencies in some places. However, it is the authors' belief that the mapping presented in this document will be adequate for the majority of cases, and will help smooth the migration to XMPP-compliant implementations.</p>
