| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This way 'extra' is unique for each connect() instance, making it safer
to mutate it, while inheriting the global settings.
See 926d53af9a7a for some more context.
|
| |
|
|
|
| |
This could happen with Dialback-only connections or others that were
missing the stream 'to' attribute.
|
| |
|
|
|
|
|
|
|
|
| |
Given an incoming <stream:stream from="example.com"> this line would
have mistakenly reported the 'from' as the local host. Neither are
technically required and may be missing, especially on connections used
only for Dialback.
Outgoing connections initiated by Prosody always have 'from_host' and
'to_host', so it is safer to check it this way.
|
| | |
|
| |
|
|
|
|
| |
Couldn't use those with the host being deactivated.
Problem: This kicks in on reload, which isn't needed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Increases log level for stream conditions that could indicate a problem
on our end, especially programming errors like invalid XML, or the
remote server saying that our certificate is invalid, since these should
be investigated.
Non-issues like closing of idle streams are lowered to debug since it's
mostly noise.
Other issues left at info are mostly about changes to the remote server,
e.g. complete or partial shutdown.
|
| |
|
|
|
|
| |
Reduces the number of left-over timers to handle after many s2s
connections were started, leaving only the ones related to incomplete
connections.
|
| |
|
|
|
|
| |
This should probably never happen, but probably does anyways.
A debug message would show the truth of the matter.
|
| |
|
|
|
| |
Nicer to get rid of a conditional that covers such a large portion of a
pretty big function.
|
| |
|
|
|
| |
These direct accesses are probably more optimized, but weird when the
module API has methods for these things.
|
| |
|
|
| |
Should have been removed in the previous commit.
|
| |
|
|
| |
See previous commit to mod_c2s: a62146353528
|
| |
|
|
|
|
|
|
|
|
| |
Fixes "attempt to compare number with nil" because `session.version` has
been cleared by s2smanager.destroy_session.
This can happen with the server_epoll setting opportunistic_writes
enabled, which means that it can notice that the connection failed at
this point, after which it triggers the whole chain of events that leads
to session destruction and "cleaning" most of the session fields.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
In "opportunistic writes" mode, prevents ondisconnect from happening
while writing the stream closing tag.
|
| |
|
|
|
|
| |
Both session.incoming and session.outgoing are truthy here, but
session.direction indicates the "real" direction in the way that matters
for the order of events when opening or closing streams.
|
| | |
|
| |
|
|
| |
Ref 115b5e32d960
|
| | |
|
| | |
|
|
|
mod_s2s.lua had been all alone in there since the removal of
s2sout.lib.lua in 756b8821007a
|
