Added a comment
This commit is contained in:
parent
403e02ecfc
commit
c0fc826f5e
1 changed files with 13 additions and 0 deletions
|
@ -0,0 +1,13 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.154.0.140"
|
||||
subject="comment 6"
|
||||
date="2013-07-21T03:07:41Z"
|
||||
content="""
|
||||
If the initiating entity includes in the initial stream header the 'version' attribute set to a value of at least \"1.0\" (see Section 4.7.5), after sending the response stream header the receiving entity MUST send a <features/> child element
|
||||
|
||||
-- <http://xmpp.org/rfcs/rfc6120.html#streams-negotiation>\"
|
||||
|
||||
By my reading this XMPP server is not RFC compliant. It's not clear to me if there's a good way for the XMPP client
|
||||
to cater to XMPP servers that neglect to send at least an empty features tag.
|
||||
"""]]
|
Loading…
Reference in a new issue