Chapril/xmpp.chapril.org-ejabberd
25
1
Fork 0
mirror of https://github.com/processone/ejabberd.git synced 2024-11-28 16:34:13 +01:00
Code Releases Activity

Update remanining old RFC links (EJAB-1728)(#444)

Browse Source
This commit is contained in:
Badlop 2015-02-26 12:18:51 +01:00
parent e10d5af303
commit 1b67ac0c20
1 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/guide.tex
View File

@ -1102,7 +1102,7 @@ request_handlers:
commonly on port 5223 for client-to-server communications. commonly on port 5223 for client-to-server communications.
But this method is nowadays deprecated and not recommended. But this method is nowadays deprecated and not recommended.
The preferable encryption method is STARTTLS on port 5222, as defined The preferable encryption method is STARTTLS on port 5222, as defined
\footahref{http://xmpp.org/rfcs/rfc3920.html\#tls}{RFC 3920: XMPP Core}, \footahref{http://xmpp.org/rfcs/rfc6120.html\#tls}{RFC 6120: XMPP Core},
which can be enabled in \ejabberd{} with the option \term{starttls}. which can be enabled in \ejabberd{} with the option \term{starttls}.
If this option is set, you should also set the \option{certfile} option. If this option is set, you should also set the \option{certfile} option.
The option \term{tls} can also be used in \term{ejabberd\_http} to support HTTPS. The option \term{tls} can also be used in \term{ejabberd\_http} to support HTTPS.
@ -1180,9 +1180,9 @@ There are some additional global options that can be specified in the ejabberd c
Default value: 'undefined'. Default value: 'undefined'.
\titem{route\_subdomains: local|s2s} \titem{route\_subdomains: local|s2s}
Defines if ejabberd must route stanzas directed to subdomains locally (compliant with Defines if ejabberd must route stanzas directed to subdomains locally (compliant with
\footahref{http://xmpp.org/rfcs/rfc3920.html\#rules.subdomain}{RFC 3920: XMPP Core}), \footahref{http://xmpp.org/rfcs/rfc6120.html\#rules-local}{RFC 6120 Local Domain rules}),
or to foreign server using S2S (compliant with or to foreign server using S2S (compliant with
\footahref{http://tools.ietf.org/html/draft-saintandre-rfc3920bis-09\#section-11.3}{RFC 3920 bis}). \footahref{http://xmpp.org/rfcs/rfc6120.html\#rules-remote}{RFC 6120 Remote Domain rules}).
\end{description} \end{description}
\makesubsubsection{listened-examples}{Examples} \makesubsubsection{listened-examples}{Examples}
@ -3951,10 +3951,9 @@ modules:
\end{verbatim} \end{verbatim}
\makesubsection{modprivacy}{\modprivacy{}} \makesubsection{modprivacy}{\modprivacy{}}
\ind{modules!\modprivacy{}}\ind{Blocking Communication}\ind{Privacy Rules}\ind{protocols!RFC 3921: XMPP IM} \ind{modules!\modprivacy{}}\ind{Blocking Communication}\ind{Privacy Rules}\ind{protocols!XEP-0016: Privacy Lists}
This module implements \footahref{http://xmpp.org/rfcs/rfc3921.html\#privacy}{Blocking Communication} This module implements \footahref{http://www.xmpp.org/extensions/xep-0016.html}{XEP-0016: Privacy Lists}.
(also known as Privacy Rules).
If end users have support for it in their \XMPP{} client, they will be able to: If end users have support for it in their \XMPP{} client, they will be able to:
\begin{quote} \begin{quote}
\begin{itemize} \begin{itemize}
@ -3974,7 +3973,6 @@ If end users have support for it in their \XMPP{} client, they will be able to:
\item Allowing or blocking all communications based on JID, group, or \item Allowing or blocking all communications based on JID, group, or
subscription type (or globally). subscription type (or globally).
\end{itemize} \end{itemize}
(from \ahrefurl{http://xmpp.org/rfcs/rfc3921.html\#privacy})
\end{quote} \end{quote}
Options: Options: