natalius wrote: Since I'm

mfoss — Tue, 04 Jan 2011 15:20:07 +0000

natalius wrote:

Since I'm using zlib compression, the starttls element is missing and we can choose either starttls or zlib. I'm writing my own jabber client.

Reading this ticket, it seems client first setups TLS, later zlib:
EJAB-499: Support Zlib compression after STARTTLS encryption

I try to login in ejabberd 2.1.6 with Psi 0.14, with three different configurations, and the WebAdmin page of the user shows three different information:

    * Psi with TLS (plain://127.0.0.1:38468#ejabberd@localhost)
    * Psi with ZLIB (zlib://127.0.0.1:38467#ejabberd@localhost)
    * Psi with TLS and ZLIB (tls+zlib://127.0.0.1:38466#ejabberd@localhost)

When I login with tls+zlib, ejabberd.log shows:

=INFO REPORT==== 4-Jan-2011::16:14:57 ===
I(<0.364.0>:ejabberd_listener:281) : (#Port<0.4430>) Accepted connection {{127,0,0,1},49676} -> {{127,0,0,1},5222}

=INFO REPORT==== 4-Jan-2011::16:14:58 ===
I(<0.404.0>:ejabberd_c2s:767) : ({socket_state,ejabberd_zlib,{zlibsock,tls,
 {tlssock,#Port<0.4430>,#Port<0.4432>},#Port<0.4434>},<0.403.0>})
 Accepted authentication for badlop by ejabberd_auth_internal

=INFO REPORT==== 4-Jan-2011::16:14:58 ===
I(<0.404.0>:ejabberd_c2s:890) : ({socket_state,ejabberd_zlib,{zlibsock,tls,
 {tlssock,#Port<0.4430>,#Port<0.4432>},#Port<0.4434>},<0.403.0>})
 Opened session for badlop@localhost/Psi with TLS and ZLIB

ejabberd - Comments for "ejabberd zlib compression"

natalius wrote: Since I'm