On Jan 13, 2009, at 9:22 AM, Jehan wrote:
Hi,
Peter Saint-Andre;6012 Wrote:
I think there may already be a bug report filed about this. I know we
discovered some strange ejabberd behavior related to compression and
TLS
at jabber.org when we required the use of TLS back in October (you
could
get around the TLS requirement if you negotiated compression first,
or
something like that).
Ok I found it:
https://support.process-one.net/browse/EJAB-499
As people said on this thread, we can see that the implementation used
by ejabberd does not include TLS compression, but apparently it is
complicated because the TLS RFC is not accurate enough about
compression
methods.
Without taking a position on whether compression is a good idea in
this context,
this bug is not really right. It's true that RFC 4346 does not specify
compressio
methods, however those are specified in RFC 3749.
-Ekr
