| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
data is received by a destroyed session
|
|
|
|
| |
outgoing s2s connection (thanks foucault)
|
| |
|
|
|
|
| |
serve, instead of a traceback (thanks stpeter)
|
|
|
|
| |
idna_to_ascii(), thanks Flo + waqas
|
|
|
|
| |
then it can could a dialback deadlock). Also remove some redundant code which could cause a db:result to be sent while still negotiating features (e.g. TLS) and break things. Collectively these fix a 'random' s2s failure (usually with ejabberd for some reason) - resulting in an 'unbound prefix' XML error, or 'ssl handshake failure'. Was this commit message long enough? I think so.
|
|
|
|
| |
connections
|
| |
|
| |
|
| |
|
|
|
|
| |
didn't advertise 1.0 (makes happy some old ejabberd versions)
|
| |
|
|
|
|
| |
stream
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
XMPP 1.0
|
| |
|
|\ |
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| | |
|
|\| |
|
| | |
|
|/
|
|
| |
session.log from the latter to the former for incoming sessions (outgoing are already like this)
|
| |
|
|
|
|
| |
fails instantly
|
| |
|
| |
|
|
|
|
| |
attempting to reconnect s2s sessions when they are closed during shutdown
|
| |
|
| |
|
| |
|
|
|
|
| |
messages and using session loggers where possible
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
back to normal.
|
| |
|
|
|
|
| |
client closes stream
|
| |
|
|
|
|
| |
issue #57)
|