Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XEP-0054: Updated error cases to be compatible with RFC 6121 #1351

Merged
merged 1 commit into from
Aug 6, 2024

Conversation

guusdk
Copy link
Contributor

@guusdk guusdk commented Jun 27, 2024

In section 3.3 of XEP-0054 it is defined that the same error condition MUST be used in both a case:

  • where a VCard request is addressed to an entity that does not exist, and;
  • where a VCard request is addressed at an entity for which no VCard is available.

RFC 6121 section 8.5.1 defines:

If the user account identified by the 'to' attribute does not exist, how the stanza is processed depends on the stanza type. For an IQ stanza, the server MUST return a <service-unavailable/> stanza error to the sender.

Prior to this change, both <service-unavailable/> and <item-not-found/> were offered as suitable conditions to be used in the error scenario defined in section 3.3. For this XEP to be more compatible with RFC 6121, only <service-unavailable> can be used.

This commit drops the <item-not-found> condition from the scenario, and elevates usage of to a MUST. It adds a note on backwards compatibility.

In section 3.3 of XEP-0054 it is defined that the same error condition MUST be used in both a case:

- where a VCard request is addressed to an entity that does not exist, and;
- where a VCard request is addressed at an entity for which no VCard is available.

RFC 6121 section 8.5.1 defines:
> If the user account identified by the 'to' attribute does not exist, how the stanza is processed depends on the stanza type. For an IQ stanza, the server MUST return a `<service-unavailable/>` stanza error to the sender.

Prior to this change, both `<service-unavailable/>` and `<item-not-found/>` were offered as suitable conditions to be used in the error scenario defined in section 3.3. For this XEP to be more compatible with RFC 6121, only <service-unavailable> can be used.

This commit drops the `<item-not-found>` condition from the scenario, and elevates usage of `<service-unavailable>` to a MUST. It adds a note on backwards compatibility.
@iNPUTmice iNPUTmice merged commit ff460a5 into xsf:master Aug 6, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants