From 4b49d8b4f1bc94be1875c077132a1ef75e0e37ea Mon Sep 17 00:00:00 2001 From: Sonny Piers Date: Sun, 22 Dec 2024 12:47:52 +0100 Subject: [PATCH] XEP-0388: Fix failure example sequence --- xep-0388.xml | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/xep-0388.xml b/xep-0388.xml index 4c854eaa6..12c660331 100644 --- a/xep-0388.xml +++ b/xep-0388.xml @@ -26,6 +26,14 @@ &dcridland; &tmolitor; &mwild; + + 1.0.3 + 2024-12-22 + sp +
    +
  • Fix failure example sequence.
  • +
+
1.0.2 2024-08-06 @@ -299,13 +307,13 @@

The <success> element is immediately followed by a <features> element in the "http://etherx.jabber.org/streams" namespace containing the applicable stream features of the newly authenticated stream. Note that no stream restart occurs.

-

A <failure/> element is used by the server to terminate the authentication attempt. It MAY contain application-specific error codes, and MAY contain a textual error. It MUST contain one of the SASL error codes from RFC 6120 Section 6.5.

+

A <failure/> element is used by the server to terminate the authentication attempt. It MAY contain a textual error and, MAY contain application-specific error codes. It MUST contain one of the SASL error codes from RFC 6120 Section 6.5.

The server MUST NOT process any inline features requested by the client in a failed authentication request, if any.

- This is a terrible example. + ]]>