| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
If it reaches this point, then the session will be most definitely be
destroyed, so try to prevent destroy_session() from being called again.
|
|
|
|
|
|
|
|
|
| |
On regular disconnects, </stream> is sent, then
sessionmanager.destroy_session() is called, then
sessionmanager.destroy_session() is called again when the TCP connection
is closed, from ondisconnect in mod_c2s.
It is a bit annoying and doesn't really tell you much.
|
|
|
|
|
|
|
| |
Should fix a traceback on attempted use after destruction, in case where
opportunistic_writes was in use.
Thanks Ge0rG
|
| |
|
|
|
|
| |
resourceprep
|
| |
|
|
|
|
| |
Taken care of by loggingmanager now
|
| |
|
| |
|
| |
|
|
|
|
| |
that for incoming
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|\| |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| | |
authenticated but unbound sessions so that resource binding is not treated as a normal stanza
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
[luacheck]
|
| |
|
|
|
|
| |
usermanager, util.xml: Add luacheck annotations
|
| |
|
|\ |
|
| |
| |
| |
| | |
'already-bound' error when client tries to bind a resource twice on the same stream (thanks Flow) fixes issue #484.
|
| |
| |
| |
| | |
say in resource binding
|
| | |
|
| |
| |
| |
| | |
traceback if stanzas are emitted after a session is destroyed (thanks Sven Blumenstein)
|
|/ |
|
| |
|
| |
|
|
|
|
| |
section-related code.
|
| |
|
| |
|
|
|
|
| |
'info')
|
|
|
|
| |
removing all cases of concatenation when building log messages
|
| |
|
|
|
|
| |
indicate failure
|
|
|
|
| |
anyway (thanks Zash)
|
| |
|
| |
|