| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| | |
The connection events are more appropriate here, where the s2s-created
events happens a bit later or earlier in a sessions lifetime depending
on its direction and for outgoing connections isn't actually the
creation time (which happens immediately after pressing enter, so not
very interesting), but rather closer to the connection time.
|
| |
| |
| |
| |
| | |
Allows doing things based on connections rather than sessions, which may
have been created before or after.
|
| |
| |
| |
| |
| | |
RFC 4627 JSON - util.json
RFC 6901 JSON Pointer - util.jsonpointer
|
| | |
|
| | |
|
| |
| |
| |
| | |
It is very often a confusing mistake that leads to support questions
|
| |
| |
| |
| | |
Makes it reachable from the shell if nothing else
|
| | |
|
| |
| |
| |
| | |
Dare to enable by default?
|
| |
| |
| |
| |
| | |
This seems like the thing to do for time, which is usually divided into
divisors divisible by 60, or multiplied by multiples of 60
|
| |
| |
| |
| | |
IANA registry files have XSLT references, which are harmless to ignore.
|
| |
| |
| |
| |
| | |
These should generally be safe to just ignore, which should be the
default behavior of Expat and LuaExpat
|
| |
| |
| |
| |
| |
| |
| | |
http://[::]:5280/ is as sensible as http://*:5280/ so why not
This might be a bit weird when listening no multiple interfaces but not
sure we can really do anything sensible then anyway.
|
| |
| |
| |
| |
| | |
This might make the global routes less confusing sometimes, or at least
valid URLs instead of http://*:5280/ which doesn't make much sense.
|
| |
| |
| |
| | |
Because why not I guess. This mirrors the corresponding luarocks command
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This way you don't need to set the server URL in the config to use this,
you could just ^C^V an install line from a web page that says
prosodyctl install https://modules.example.com/mod_example.src.rock
Drop the help message in this case since it'll be all messed up by being
given an URL or rock filename.
|
| |
| |
| |
| |
| | |
Only when the help is shown because of invalid arguments should a
non-zero status code be returned to indicate a problem.
|
| |
| |
| |
| | |
Reads nicer, but adds more code. Can always be reverted later I suppose.
|
| |
| |
| |
| |
| |
| |
| | |
This way the host-agnostic http://*:5280/ handler is not enabled, but
BOSH can still be used with any local VirtualHost
Ref #1712
|
| |
| |
| |
| |
| |
| |
| | |
This way the host-agnostic http://*:5280/ handler is not enabled, but
BOSH can still be used with any local VirtualHost
Ref #1712
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Metadata in modules is added using lines formatted as:
--% key: value
Where key is a valid identifier string, and value is also a string (leading
and trailing whitespace are trimmed during parsing).
The initial supported keys are:
--% requires_core_features: feature1, feature2, ...
--% conflicts_core_features: feature1, feature2. ...
These 'features' map to features reported by the new core.features module.
A benefit of this load-time metadata approach compared to e.g. something like
module:requires()/module:conflicts() is that we can continue to look in module
search paths for a suitable module. Aborting an already-loaded module due to
a version conflict would be too late.
|
| | |
|
| |
| |
| |
| |
| | |
A "feature" is a simple string, and it's expected that we will add to (and
maybe remove from) this list over the course of time.
|
| |
| |
| |
| |
| | |
Load filters can choose to block the loading of certain files, and optionally
return some metadata about the loaded file.
|
| | |
|
| |
| |
| |
| |
| | |
Extra-extra obvious that no interaction with this should lead to
persisted changes
|
| |
| |
| |
| |
| | |
I'm not sure what went wrong here, copy-paste mistake?
Doesn't matter as long as nobody can create nodes on this service.
|
| |
| |
| |
| |
| | |
Currently it is hard codded to be a specialized stdout logger, which
should be fixed one day.
|
| |
| |
| |
| | |
Especially 'connectivity' was missing
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Original motivation was tiresome warnings about Lua 5.4 not being
supported yet.
Can still be handy to tweak log level, e.g. to prevent logging to
interfere with command output.
|
| |
| |
| |
| | |
Filtered trough pandoc
|
| |
| |
| |
| | |
Now based on draft-ietf-dnsop-svcb-https-08
|
| |
| |
| |
| | |
Based on draft-ietf-dnsop-svcb-https-00
|
| |
| |
| |
| |
| |
| | |
Doesn't affect normal usage by Prosody since neither A nor AAAA records
use this and SRV records has the host name last so the position is not
needed.
|
| |
| |
| |
| |
| | |
Note the duplicate 9 and 16 entries, neither of which are especially
relevant for our resolver usage.
|
| | |
|
| |
| |
| |
| |
| | |
Goal is to regenerate this file from the IANA registry using a tool.
Having it in a separate file will reduce vcs noise in util.dns
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Probably worked anyway but settings might not always have been applied
depending on what order things happens in.
Error was hidden by the pcall, which was sorta intentional...
|
| |
| |
| |
| |
| | |
We break the SHOULD about the merged _xmpp and _xmpps SRV handling, but
we follow all the MUSTs
|