| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Some confusion happened in 42b98ee73ca8, possibly because .count()
returns the items?
|
|
|
|
|
|
|
| |
This clone call was lost in 902d25cd0557
Affects e.g. presence broadcasts, where the same stanza is sent many
times while mutating the 'to' attribute.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This queue is used to buffer stanzas while waiting for an outgoing s2s
connection to be established.
Limit it to prevent excessive memory usage.
Default chosen to approximate how many average stanzas fits in the
server_epoll default max_send_buffer_size of 32 MiB
Returns a custom error instead of the default core.stanza_router
"Communication with remote domains is not enabled" from is sent back,
which does not describe what is happening here.
Closes #1106
|
|
|
|
|
| |
Reduces duplication and need to edit in two places when adding another
metadata field.
|
|
|
|
|
| |
No longer bypasses access control to retrieve this config subset, which
is also explicitly named in the service config now.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously the error messages said that it failed to "publish" to PEP, but
sometimes a sync involves removing items, which can be confusing.
The log was also the same for both legacy PEP and private XML bookmarks.
Having different log messages makes it easier to debug the cause and location
of any sync errors.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It appears that when:
1) The user has no bookmarks 2 node in PEP
2) The client publishes an empty bookmark set to a legacy bookmarks location
3) mod_bookmarks will attempt to purge items from the non-existent node and
log an error about the failure (item-not-found).
This new code will suppress an item-not-found error from the purge operation
in the empty-bookmarks case, and adds a log message for any other error (this
is helpful because the existing log message confusingly says it was an error
*publishing* to the node, which isn't always accurate).
|
| |
| |
| |
| | |
No, that wasn't running in a thread, but in a next tick timer.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Prevents ASYNC-01 due to storage interactions in a timer.
Also considered modifying mod_c2s to allow passing arbitrary closures
into its runner thread but this seems like a big step away from the
current code for just this module.
Also considered creating a dedicated runner in mod_smacks, but ensuring
continuity across module reloads might be tricky.
We could further improve this in the next major version.
|
| |
| |
| |
| | |
The three-argument version seems to be a left-over from 0.12
|
| |
| |
| |
| |
| | |
Roles for JIDs outside the current host are derived from configuration
only with this module.
|
| |
| |
| |
| | |
mod_authz_internal does not support this
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Removes dependency on util.error from util.pubsub which was only used
for this one special case.
Line count reduction!
Would be even nicer if templating could be done by util.error itself.
|
| |
| |
| |
| | |
Continuation of 4b39691a274e
|
| |
| |
| |
| | |
Sometimes it is useful to pass additional information along.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is what util.error was made for!
This replaces the custom error stanza builder with common code in
util.stanza that knows enough about util.error and namespaced errors.
Some awkwardness remains in the way util.pubsub returns conflicting
form fields.
|
|\| |
|
| |
| |
| |
| | |
Also rename for loop item so that it doesn't shadow module variable.
|
| |
| |
| |
| |
| |
| | |
To support cases where the admin does not have easy access to the
command line to generate a password reset invite for someone who forgot
their password.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This enables granting regular users permission to create nodes via the
new roles framework. Previously this required either making everyone an
admin or writing a custom mod_pubsub variant with different permission
details.
Previous default behavior of only allowing creation by admin is kept as
to not give out unexpected permissions on upgrade, but could be
reevaluated at a later time.
Fixes #1324
|
| | |
|
| | |
|
| |
| |
| |
| | |
Consistency.
|
|\| |
|
| | |
|
| |
| |
| |
| | |
Here too
|
| |
| |
| |
| | |
The code assumed a 2-d sparse array but it could also be a string.
|
| |
| |
| |
| | |
I did not measure, but this should be way fewer function calls.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Throws error attempting to append the nil label list to an array for
host-scoped metrics.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
test_password()
This API method is used e.g. in HTTP modules which also should respect
disabled accounts.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is the time after liveness checks are performed via the respective
read-timeout event, which by default involves sending a space character
but could be overridden e.g. as is done by mod_smacks.
Only advertised, unsure what we would do with it.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change has various technical and social benefits. If ownership of a MUC
is really needed, it can be gained using the 'Set affiliation' ad-hoc command
or prosodyctl shell.
Example client incompatibility with the old behaviour:
- https://github.com/monal-im/Monal/issues/1085
|
| |
| |
| |
| | |
Based on mod_muc_restrict_pm in prosody-modules d82c0383106a
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Only supporting exact match on full JID isn't helpful if you want to
list sessions per host or user.
Backport of 430333198e4c
Fixes #1857
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
compliant behavior
From XEP-0191:
> For message stanzas, the server SHOULD return an error, which SHOULD
> be <service-unavailable/>.
Following this may leak to a blocked JID that they have been blocked,
which seems contrary to the goal of pretending to be perpetually
offline.
|
| |
| |
| |
| |
| |
| |
| | |
Allows e.g. restricting your vcard4 to only family or similar.
Notes: This does not include roster groups in the configuration form,
so the client will have to get them from the actual roster.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Returning nothing/nil lets stanzas pass, returning anything else blocks
|
| |
| |
| |
| |
| | |
This ensures that someone on your blocklist is unable to invite you to MUC
rooms.
|
| | |
|
| |
| |
| |
| | |
Similar to 26c30844cac6
|
| |
| |
| |
| | |
`result[, err]`, not `ok, err|result`, must have confused it with pcall
|