| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| | |
http://lua.sqlite.org/
|
| |
| |
| |
| | |
Introduced in dbe9781fd278
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
configured (fix #1793)
Existing such records may cause timeouts or errors in clients and
servers trying to connect, despite prosodyctl check saying all is well
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This is required by PASETO v3.local
|
| |
| |
| |
| | |
These are needed for PASETO v3.local.
|
|\| |
|
| |
| |
| |
| | |
To mirror behavior of prosodyctl invocation
|
| |
| |
| |
| |
| | |
Frees unneeded resources earlier, so they're not held on to while
potentially sending the chunk trailer.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Unregistering the response before sending the trailer of the chunked
transfer encoding prevents opportunistic writes from being invoked and
running this code again when, which may cause an error when closing the
file handle a second time.
Normally the file size is known, so no chuck headers are sent.
|
|\| |
|
| |
| |
| |
| | |
Patch by Peter Kieser
|
| |
| |
| |
| |
| |
| |
| | |
Main difference is that timers are not checked unconditionally before
each poll, only when running out of previous poll results (hidden by
util.poll). This removes a final poll at shutdown that usually delays
the 'not quitting' condition check by one second.
|
| |
| |
| |
| |
| | |
This isn't actually used in Prosody, so no value in complicating the
real main loop because of it
|
|\| |
|
| |
| |
| |
| | |
Transplanted 6b43bf85032b from trunk
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes `prosodyctl adduser` etc.
Prior to d580e6a57cbb the line did nothing.
Sometimes storage in the prosodyctl context does cause weirdness, as it
is not in a host context, but rather a variant of global.
|
| | |
|
| |
| |
| |
| |
| | |
This allows for modules to update fields, which is generally better than
maintaining this hard-coded list of transferable properties here.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Don't need the function, more compact to just reference the same
reference table.
|
| |
| |
| |
| | |
See bd9e006a7a74 for more context
|
| |
| |
| |
| |
| |
| |
| | |
Secure delegation or "Mini-DANE"
As with the existing DANE support, only usable in one direction, client
certificate authentication will fail if this is relied on.
|
| |
| |
| |
| | |
Will be useful even later...
|
| |
| |
| |
| | |
Will be useful later.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The order of checks led to Bogus results being reported with a generic
"unable to resolve service". This had no practical effects as such
results are simply empty and the process would stop there.
Tested by attempting to establish s2s with dnssec-bogus.sg and observing
the error reply.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Having mod_s2s know about the bidi namespace is perhaps a bit awkward
but putting this in mod_s2s_bidi would be more awkward as it has nothing
to do with limits. Some indirection event could be added in the future.
|
| | |
|
| |
| |
| |
| | |
As introduced in XEP-xxxx: Stream Limits Advertisement
|
| |
| |
| |
| | |
Thanks MattJ
|
| |
| |
| |
| |
| |
| |
| |
| | |
Just dropping them isn't great but hopefully something more sensible can
be done in the future.
Will need work to ensure that this signal is handled correctly in
sending modules etc.
|
| |
| |
| |
| | |
For future use, i.e. canceling sending of stanzas that exceed the limit
|
| |
| |
| |
| | |
So they can, like, not send big stanzas.
|
| |
| |
| |
| |
| |
| |
| | |
Should help clients avoid sending stanzas that will get their stream
killed. Custom namespace while ironing out the protocol.
My spoon is too big!
|
| |
| |
| |
| | |
So that happens in a single place, where it can be changed easier.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Required due to track_session() having moved here
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In this API, a 'node' is always a simple text string. Sometimes the caller may
have a more complex structure representing a node, but the hash ring is really
only concerned with the node's name.
This API change allows :add_nodes() to take a table of `node_name = value`
pairs, as well as the simple array of node names previously accepted.
The 'value' of the selected node is returned as a new second result from
:get_node().
If no value is passed when a node is added, it defaults to `true` (as before,
but this was never previously exposed).
|
| |
| |
| |
| | |
sequential style
|
| |\ |
|
| |\ \ |
|