Programming Jabber

Password Errors and Retries

If you don’t supply all the required parameters, you are notified with a 406 “Not Acceptable” error:

SEND: <iq type='set'>
        <query xmlns='jabber:iq:auth'>
          <username>dj</username>
          <digest>03ea09f012493415908d63dcb1f6dbdb9bfc09ba</digest>
        </query>
      </iq>

RECV: <iq type='result' id='pthsock_client_auth_ID'>
        <query xmlns='jabber:iq:auth'>
          <username>dj</username>
          <digest>03ea09f012493415908d63dcb1f6dbdb9bfc09ba</digest>
        </query>
        <error code='406'>Not Acceptable</error>
      </iq>

In this case, no <resource/> value was supplied. The <resource/> value is required, as it is the key part of the JID that is used to distinguish between multiple connections as the same user on the same Jabber server.

If you get the password wrong, you receive a 401 “Not Authorized” error. There is currently no limit on the number of times an authorization attempt can be made, but the <karma/> limits for the c2s connections (see Chapter 5) may slow the attempts down.