Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | doap: Reference some JSON RFCs | Kim Alvefur | 2022-02-05 | 1 | -0/+2 |
| | | | | | RFC 4627 JSON - util.json RFC 6901 JSON Pointer - util.jsonpointer | ||||
* | doap: Reference RFC 6331 which deprecated SASL DIGEST-MD5 | Kim Alvefur | 2022-02-05 | 1 | -0/+1 |
| | |||||
* | prosody.cfg.lua.dist: Link to website (thanks eta) | Kim Alvefur | 2021-07-17 | 1 | -0/+2 |
| | |||||
* | prosody.cfg.lua.dist: Warn about adding settings at the end of the file | Kim Alvefur | 2021-07-17 | 1 | -0/+9 |
| | | | | It is very often a confusing mistake that leads to support questions | ||||
* | core.modulemanager: Save module metadata for potential later use | Kim Alvefur | 2022-02-05 | 1 | -1/+2 |
| | | | | Makes it reachable from the shell if nothing else | ||||
* | util.startup: Enable DANE in http client library with use_dane | Kim Alvefur | 2022-02-05 | 1 | -0/+1 |
| | |||||
* | net.http: Allow using DANE via options or per request settings | Kim Alvefur | 2022-02-05 | 1 | -1/+5 |
| | | | | Dare to enable by default? | ||||
* | mod_smacks: Tweak resumption age buckets towards multiples of 60 | Kim Alvefur | 2022-02-04 | 1 | -1/+1 |
| | | | | | This seems like the thing to do for time, which is usually divided into divisors divisible by 60, or multiplied by multiples of 60 | ||||
* | tools: Allow processing instructions in some XML parsing tools | Kim Alvefur | 2022-02-04 | 2 | -2/+2 |
| | | | | IANA registry files have XSLT references, which are harmless to ignore. | ||||
* | util.xml: Add an option to allow <?processing instructions?> | Kim Alvefur | 2022-02-04 | 2 | -1/+11 |
| | | | | | These should generally be safe to just ignore, which should be the default behavior of Expat and LuaExpat | ||||
* | mod_http: Use interface name as default default global hostname | Kim Alvefur | 2022-02-04 | 1 | -1/+1 |
| | | | | | | | 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. | ||||
* | mod_http: Use http_default_host for URLs generated in global context | Kim Alvefur | 2022-02-04 | 1 | -1/+2 |
| | | | | | This might make the global routes less confusing sometimes, or at least valid URLs instead of http://*:5280/ which doesn't make much sense. | ||||
* | prosodyctl: Allow passing server on command line with --server | Kim Alvefur | 2022-02-04 | 1 | -1/+1 |
| | | | | Because why not I guess. This mirrors the corresponding luarocks command | ||||
* | prosodyctl: Allow install plugin via explicit path or URL | Kim Alvefur | 2022-02-04 | 1 | -2/+2 |
| | | | | | | | | | | 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. | ||||
* | prosodyctl: Return success status code from --help | Kim Alvefur | 2022-02-04 | 1 | -11/+11 |
| | | | | | Only when the help is shown because of invalid arguments should a non-zero status code be returned to indicate a problem. | ||||
* | prosodyctl: Use argument parsing library to parse --help, -h, -? | Kim Alvefur | 2022-02-04 | 1 | -12/+27 |
| | | | | Reads nicer, but adds more code. Can always be reverted later I suppose. | ||||
* | mod_websocket: Only enable host-agnostic HTTP routing when enabled globally | Kim Alvefur | 2022-02-04 | 1 | -1/+3 |
| | | | | | | | This way the host-agnostic http://*:5280/ handler is not enabled, but BOSH can still be used with any local VirtualHost Ref #1712 | ||||
* | mod_bosh: Only enable host-agnostic HTTP routing when enabled globally | Kim Alvefur | 2022-02-04 | 1 | -1/+3 |
| | | | | | | | This way the host-agnostic http://*:5280/ handler is not enabled, but BOSH can still be used with any local VirtualHost Ref #1712 | ||||
* | util.format: Fix typo in comment [codespell] | Kim Alvefur | 2022-02-04 | 1 | -1/+1 |
| | |||||
* | mod_pep: Fix typo in comment [codespell] | Kim Alvefur | 2022-02-04 | 1 | -1/+1 |
| | |||||
* | mod_bookmarks: Fix typos in stanza error messages [codespell] | Kim Alvefur | 2022-02-04 | 1 | -2/+2 |
| | |||||
* | mod_admin_shell: Fix typo in comment [codespell] | Kim Alvefur | 2022-02-04 | 1 | -1/+1 |
| | |||||
* | modulemanager: Shorten metadata keys to improve readability and memorability | Matthew Wild | 2022-02-04 | 1 | -5/+5 |
| | |||||
* | Revert util.debug change accidentally committed in e157e5c79daa | Matthew Wild | 2022-02-04 | 1 | -1/+1 |
| | |||||
* | util.pluginloader: Fix method to return any module metadata (luacheck) | Matthew Wild | 2022-02-04 | 1 | -1/+1 |
| | |||||
* | modulemanager: Add plugin load filter that reads module metadata from source | Matthew Wild | 2022-02-04 | 1 | -0/+32 |
| | | | | | | | | | | | | | | | | | | | | | 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. | ||||
* | modulemanager, moduleapi: Switch to new pluginloader interface | Matthew Wild | 2022-02-04 | 2 | -4/+9 |
| | |||||
* | core.features: New module to track and expose the features supported by Prosody | Matthew Wild | 2022-02-04 | 1 | -0/+8 |
| | | | | | 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. | ||||
* | util.pluginloader: Support for a per-file load filter | Matthew Wild | 2022-02-03 | 1 | -6/+14 |
| | | | | | Load filters can choose to block the loading of certain files, and optionally return some metadata about the loaded file. | ||||
* | util.pluginloader: Support for multiple pluginloader instances, and options | Matthew Wild | 2022-02-03 | 2 | -11/+29 |
| | |||||
* | mod_pep: Clarify purpose of fallback service | Kim Alvefur | 2022-02-03 | 1 | -0/+7 |
| | | | | | Extra-extra obvious that no interaction with this should lead to persisted changes | ||||
* | mod_pep: Correct initialization of fallback service | Kim Alvefur | 2022-02-03 | 1 | -8/+6 |
| | | | | | I'm not sure what went wrong here, copy-paste mistake? Doesn't matter as long as nobody can create nodes on this service. | ||||
* | core.loggingmanager: Add FIXME about supporting console logging to stderr | Kim Alvefur | 2022-02-02 | 1 | -0/+1 |
| | | | | | Currently it is hard codded to be a specialized stdout logger, which should be fixed one day. | ||||
* | man/prosodyctl: Complete list of 'check' variants | Kim Alvefur | 2022-02-02 | 2 | -3/+4 |
| | | | | Especially 'connectivity' was missing | ||||
* | man/prosodyctl: Clarify description of --root | Kim Alvefur | 2022-02-02 | 2 | -2/+2 |
| | |||||
* | util.startup: Teach prosodyctl to be completely --silent | Kim Alvefur | 2021-11-28 | 3 | -0/+9 |
| | |||||
* | util.startup: Teach prosodyctl to be --quiet as complement to --verbose | Kim Alvefur | 2021-11-28 | 3 | -3/+21 |
| | | | | | | | | 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. | ||||
* | man/prosodyctl: Normalize formatting syntax | Kim Alvefur | 2022-02-02 | 2 | -115/+63 |
| | | | | Filtered trough pandoc | ||||
* | util.dns: Minor updates of SVCB parser | Kim Alvefur | 2022-02-02 | 1 | -1/+2 |
| | | | | Now based on draft-ietf-dnsop-svcb-https-08 | ||||
* | util.dns: Implement SVCB record parser | Kim Alvefur | 2020-10-04 | 1 | -0/+54 |
| | | | | Based on draft-ietf-dnsop-svcb-https-00 | ||||
* | util.dns: Fix returning read position after zero-length name | Kim Alvefur | 2020-10-04 | 1 | -1/+1 |
| | | | | | | 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. | ||||
* | util.dnsregistry: Regenerate from IANA registry | Kim Alvefur | 2022-02-02 | 1 | -57/+120 |
| | | | | | Note the duplicate 9 and 16 entries, neither of which are especially relevant for our resolver usage. | ||||
* | tools.dnsregistry: For converting IANA DNS registry data to Lua table | Kim Alvefur | 2020-10-04 | 1 | -0/+43 |
| | |||||
* | util.dns: Move DNS parameters details into util.dnsregistry | Kim Alvefur | 2020-10-04 | 2 | -56/+63 |
| | | | | | 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 | ||||
* | doap: Make note of mod_mam storing XEP-0184 receipts | Kim Alvefur | 2021-03-18 | 1 | -0/+8 |
| | |||||
* | plugins: Update for namespace bump in XEP-0353 v0.4.0 | Kim Alvefur | 2022-01-11 | 4 | -4/+4 |
| | |||||
* | util.prosodyctl.check: Fix reset of libunbound before DNS checks | Kim Alvefur | 2022-02-01 | 1 | -1/+1 |
| | | | | | | | 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... | ||||
* | doap: Let's say XEP-0368 support is complete now | Kim Alvefur | 2022-01-31 | 1 | -1/+1 |
| | | | | | We break the SHOULD about the merged _xmpp and _xmpps SRV handling, but we follow all the MUSTs | ||||
* | util.prosodyctl.check: Fix A/AAAA check for proxy65 and http | Kim Alvefur | 2022-01-30 | 1 | -2/+2 |
| | | | | | | When there are no records to return the return value from dns.lookup() might be nil or might be a table containing zero records, depending on which DNS library is used | ||||
* | util.prosodyctl.check: Include multiplexed ports in DNS checks #1704 | Kim Alvefur | 2022-01-30 | 1 | -0/+13 |
| |