| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This line was copied from mod_mam, where `origin.username` made sense,
less so here.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is becoming more common in XMPP as people experiment with a MIX-like
model where the bare JID joins a group chat instead of a full JID.
Specifically right now this is being added to help with processing
notifications from mod_muc_offline_delivery.
|
| | |
| | |
| | |
| | |
| | |
| | | |
The intent is to ensure 'ondisconnect' only gets called once, while
giving buffered outgoing data a last chance to be delivered via the
:close() path in case the connection was only shutdown in one direction.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before 22825cb5dcd8 connection attempts that failed (e.g. connection
refused) would be immediately destroyed. After, it would schedule
another write cycle and then report 'ondisconnect' again when failing.
Thanks Martin for reporting
|
|\| | |
|
| | |
| | |
| | |
| | | |
Should ensure shutdown even if sockets somehow take a very long to get closed.
|
| | |
| | |
| | |
| | |
| | | |
This should ensure that sockets get closed even if they are added after
the quit signal. Otherwise they may keep the server alive.
|
| | |
| | |
| | |
| | |
| | |
| | | |
lfs or WHAT
How did this even happen?
|
| | | |
|