| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Seems more suitable than asking if prosodyctl was meant to be used, or
going ahead and starting.
|
|
|
|
|
| |
Better than duck typing, in case anyone ever passes a non-stanza table
with a 'name' field.
|
|
|
|
|
|
|
| |
`reason` was often a table, so the log said "table: 0xptr" or such.
mod_c2s, mod_bosh etc logs the stream error stanza object, so better do
the same. It would be nicer if this was an util.error object, but that
will have to be a future change.
|
|
|
|
|
|
| |
This field is empty for reasons when invoked by prosody-migrator, which
threw an error:
> bad argument #1 to 'open' (string expected, got nil)
|
| |
|
|
|
|
|
|
|
| |
If the request fails in the middle then the file~ could be left behind
because no code was invoked to delete it then. This gets rid of it when
the request is removed. It may still be left in case of an unclean
shutdown.
|
| |
|
|
|
|
| |
Context in #1006 and revisions 89c42aff8510 e1d274001855
|
|
|
|
|
|
|
|
| |
Makes it easier to find XEPs that have had new revisions since we last
looked at them and the corresponding code.
A review of changelogs between these versions point to mostly editorial
changes or otherwise without warrant for code changes.
|
|
|
|
|
| |
Makes it easier to find XEPs that have had new revisions since we last
looked at them and the corresponding code.
|
|
|
|
|
| |
Labels are supposed to be fixed sets of things, so defined hosts are
okay, but not unknown hosts.
|
|
|
|
|
|
|
| |
Should call timers less frequently when many sockets are waiting for
processing. May help under heavy load.
Requested by Ge0rG
|
|
|
|
|
|
| |
Can't find anything saying anything on whether this is needed or not.
kawaii reported that both Chrome and Firefox complained unless the
header was added to the list of allowed headers.
|
|
|
|
|
|
| |
Clients would generally be using the "max" symbol instead of discovering
this, but this also gets us validation and earlier rejection of out of
bounds values.
|
|
|
|
|
|
|
| |
Disable persistence instead if no items should be persisted.
XEP-0060 is not entirely clear on what either of those option really
mean.
|
|
|
|
|
|
|
|
| |
Default left as 'never' in mod_pubsub to preserve the previous behavior.
Unclear if this is desirable, but can always be changed later.
In mod_pep this allows turning off the automatic resending of most
recent item.
|
|
|
|
|
|
|
| |
This is as per the HTTP standards [1]. Thankfully, the REQUIRED
www-authenticate header is already generated by the code.
[1]: https://datatracker.ietf.org/doc/html/rfc7235#section-3.1
|
|
|
|
| |
mod_auth_ldap provides LDAP support without being tied to Cyrus
|
| |
|
|
|
|
|
| |
Because it's nice, not having to find it in http:list(), which could
have a lot of items.
|
| |
|
| |
|
|
|
|
| |
#1692)
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
In some data dumps, presumably from newer ejabberd versions, position 5 is
the string "sha", and the iteration count follows it.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is not a pretty way to signal this... but it is the current API
interface:inittls() is a new code path which did not go past the point
in interface:starttls() where it set starttls to false, leading mod_tls
to offer starttls on direct TLS connections
Thanks Martin for discovering.
|
| | |
|
| | |
|
| |
| |
| |
| | |
We're doing our best!
|
| | |
|
| |
| |
| |
| |
| |
| | |
The default of 0.001..100.0 did not feel suitable here. This might be
better. Longer is better and hold times less than a few seconds is
generally undesirable.
|
| | |
|
|\| |
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
Mirroring the internal API
|
| | |
| | |
| | |
| | |
| | | |
Previously it would default to exit with 0 as status code, meaning
success, which is weird.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
prosodyctl
Makes it clearer that prosody does not take -v atm, as well as how
prosodyctl does not take the demonization flags.
|
| | |
| | |
| | |
| | | |
More convenient than the environment variable.
|
| | |
| | |
| | |
| | |
| | | |
Reduces the reliance on observe.jabber.network and enables alternatives
for those who wish to have that.
|
| | |
| | |
| | |
| | |
| | | |
Feels a bit cleaner to hide away the async.waiter() and return value
handling. Also line count reduction!
|
| | |
| | |
| | |
| | |
| | |
| | | |
To prevent a situation where you for whatever reason use a full JID that
is currently online and the response ends up routed there instead of the
module:send_iq() handlers.
|
| | |
| | |
| | |
| | |
| | | |
Since we don't currently have hooks that includes type and id here, we
need to check those attributes in the handlers.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is primarily something that happens with an internal query to
mod_mam, which calls origin.send() several times with results, leading
to the first such result being treated as the final response and
resolving the promise.
Now, these responses pass trough to the underlying origin.send(), where
they can be caught. Tricky but not impossible. For remote queries, it's
even trickier, you would likely need to bind a resource or similar.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Per the unspoken internal standard of -1 as priority for most built-in
event handlers, since this makes it easy for 3rd party plugins to
override behavior by hooking at the default priority of 0.
|