| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Makes it symmetric with parsing.
|
| |
| |
| |
| |
| | |
Makes more sense than coercing to a string, which would always be
truthy.
|
| | |
|
| |
| |
| |
| |
| | |
prosodyctl -h showing an error was not very helpful, especially since
prosodyctl shows its help for any unknown (or none) command.
|
| |
| |
| |
| |
| | |
Seems more suitable than asking if prosodyctl was meant to be used, or
going ahead and starting.
|
| |
| |
| |
| |
| |
| | |
This field is empty for reasons when invoked by prosody-migrator, which
threw an error:
> bad argument #1 to 'open' (string expected, got nil)
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
mod_auth_ldap provides LDAP support without being tied to Cyrus
|
| |
| |
| |
| | |
#1692)
|
|\| |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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!
|
| |
| |
| |
| | |
Remember to remove the compatibility things in some future version
|
| |
| |
| |
| | |
It's basically deprecated
|
| |
| |
| |
| | |
The singulars are supposed to be deprecated
|
| |
| |
| |
| |
| | |
All 'net' providers generate a _port option which must be in the global
section, but this mistakenly also warns about these options as well.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Behaviour follows the same logic as string.sub (so yes, 1-indexed).
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Other tests don't require a running prosody and I forgot to start it
when testing.
|
| |
| |
| |
| |
| |
| |
| | |
This uses the (experimental) observe.jabber.network API to
perform external connectivity checks. The idea is to complement
the checks prosodyctl can already do with a (nearly) complete
s2s/c2s handshake from a remote party to test the entire stack.
|
| |
| |
| |
| | |
And to follow existing naming practices better than 'legacy_ssl' did.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Hopefully this will eventually be upgraded to RSM, which is why the
argument is called 'resultspec' and is a table.
|
| |
| |
| |
| |
| | |
Also special thanks to timeless, for wordlessly reminding me to check
for typos.
|
| |
| |
| |
| |
| |
| | |
XEP-0060 says that this the way to indicate that 'persistent-items' is
unsupported, but doesn't explicitly say if it being disabled in the node
configuration also counts as unsupported.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When set to 'false' there is no need for a persistence interface at all,
since items are not persisted after being broadcast.
Had started wondering if maybe the behavior was wrong, after reading
parts of XEP-0060 that pointed in that direction.
Some discussion of this can be found in logs of
xmpp:xsf@muc.xmpp.org?join from around 2021-07-20
Thanks to Ralph for confirming.
|
| |
| |
| |
| |
| |
| | |
Since nodes were always persistent according to the XEP-0060 definition.
Whether data is stored in memory or on disk was not what this setting
was meant for.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is in preparation for fixing the behavior of 'persist_items', which
was misunderstood at some point. In mod_pep it toggles between
persistent storage and in-memory storage, while the correct behavior
would be to toggle whether published items are stored at all or
forgotten after being broadcast.
|
| | |
|
| |
| |
| |
| |
| |
| | |
In some cases you might end up with both 'xmpp.example.com' and
'xmpp.example.com.', which are the same thing so no point in doing the
same checks twice.
|
| |
| |
| |
| |
| |
| | |
Clients would try to connect and receive an error or timeout, increasing
the time it takes to establish a connection. Probably not what you want.
If you really want IPv6 or IPv4 disabled, best remove the A or AAAA record.
|
| |
| |
| |
| | |
Why would you do this?!
|
| |
| |
| |
| |
| | |
If you set 'use_ipv4 = false' then you probably don't care much for the
host not resolving to the IPv4 address, and same with 'use_ipv6'.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This may have mistakenly caused link-local addresses to be considered
global. May have caused mod_s2s and prosodyctl check dns to behave
incorrectly on networks using link-local IPv4 addresses. By my
guesstimate, these are extremely rare. Probably minimal impact beyond
a bit longer to establish s2s and some possible confusion from
prosodyctl check dns results.
Ref RFC 3927
|
| | |
|
| |
| |
| |
| |
| | |
This should a) prevent injection of text that looks like legitimate log
lines and b) not mangle tracebacks.
|
| |
| |
| |
| |
| | |
Made the pattern match a longer range than intended, but with no effect
since those characters are not present in the 'control_symbols' table.
|
| |
| |
| |
| |
| |
| | |
If unbound was initialized prior to this then the config change here
wouldn't apply, and it will again think that 127.0.1.1 has been found
in DNS.
|
| | |
|
| | |
|