| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | | mod_http_file_share: Handle content-type being optional | Kim Alvefur | 2021-01-27 | 1 | -2/+2 | |
| | | | ||||||
| * | | mod_http_file_share: Reject invalid file sizes | Kim Alvefur | 2021-01-27 | 2 | -0/+17 | |
| | | | ||||||
| * | | mod_http_file_share: Fix name of max-file-size tag | Kim Alvefur | 2021-01-27 | 1 | -1/+1 | |
| | | | ||||||
| * | | mod_http_file_share: Expand registry to fix extra tag | Kim Alvefur | 2021-01-27 | 1 | -5/+6 | |
| | | | | | | | | | | | Error registry compact format doesn't support extra.tag so needs to be the more verbose format | |||||
| * | | mod_http_file_share: Verify final file size on completion of upload | Kim Alvefur | 2021-01-27 | 1 | -0/+5 | |
| | | | ||||||
| * | | mod_http_file_share: Add file type filter | Kim Alvefur | 2021-01-26 | 3 | -0/+20 | |
| | | | | | | | | | | | Unlike mod_http_upload, this can't be bypassed by uploading with a different file extension. | |||||
| * | | mod_http_file_share: Add file size limit (default 10M) | Kim Alvefur | 2021-01-26 | 3 | -0/+30 | |
| | | | ||||||
| * | | mod_http_file_share: Validate that filename does not contain '/' | Kim Alvefur | 2021-01-26 | 2 | -0/+19 | |
| | | | ||||||
| * | | mod_http_file_share: Return proper error if unauthorized | Kim Alvefur | 2021-01-26 | 1 | -1/+5 | |
| | | | ||||||
| * | | mod_http_file_share: Add basic access control | Kim Alvefur | 2021-01-26 | 1 | -1/+7 | |
| | | | | | | | | | Partly lifted from mod_external_services | |||||
| * | | mod_http_file_share: Add support for external file upload service | Kim Alvefur | 2021-01-26 | 2 | -3/+9 | |
| | | | | | | | | | | | PUT /upload/:slot/:filename Authorization: Bearer JWT{ uploader, filename, filesize, filetype, exp } | |||||
| * | | mod_http_file_share: Let's write another XEP-0363 implementation | Kim Alvefur | 2021-01-26 | 5 | -0/+229 | |
| | | | | | | | | | | | | | | | | | | | | | This variant is meant to improve upon mod_http_upload in some ways: * Handle files much of arbitrary size efficiently * Allow GET and PUT URLs to be different * Remember Content-Type sent by client * Avoid dependency on mod_http_files * Built-in way to delegate storage to another httpd | |||||
| * | | util.interpolation: Add test for #1623 | Kim Alvefur | 2021-01-25 | 1 | -0/+5 | |
| | | | ||||||
| * | | Merge 0.11->trunk | Kim Alvefur | 2021-01-25 | 1 | -2/+2 | |
| |\| | ||||||
| | * | util.interpolation: Fix combination of filters and fallback values #1623 | Kim Alvefur | 2021-01-25 | 1 | -2/+2 | |
| | | | ||||||
| * | | util.startup: Make installer_plugin_path relative to data directory | Kim Alvefur | 2021-01-24 | 1 | -3/+2 | |
| | | | | | | | | | | | | | Having it relative to current working directory is problematic since this depends on how Prosody was started and changes to the data directory during startup (but after this point). | |||||
| * | | util.startup: Don't create installer plugin path (as root) | Kim Alvefur | 2021-01-24 | 1 | -2/+0 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since this runs before dropping root, the directory ends up being owned by root, resulting in luarocks failing to install anything, since by then it would be running as the prosody user. luarocks creates this directory if needed, so creating it during startup is not necessary. One potential issue is if the directory is somewhere where Prosody can't write, but then you will simply have to create it yourself with the appropriate permissions. | |||||
| * | | util.prosodyctl.check: Recognise global options related to plugin installer | Kim Alvefur | 2021-01-21 | 1 | -0/+1 | |
| | | | ||||||
| * | | net.unbound: Fix to initialize under prosodyctl | Kim Alvefur | 2021-01-21 | 1 | -0/+1 | |
| | | | | | | | | | | | Lazy initialization only worked for async queries, but prosodyctl check dns uses sync queries. | |||||
| * | | prosodyctl: Add reference to #1602 (plugin installer docs) in comment | Kim Alvefur | 2021-01-21 | 1 | -0/+1 | |
| | | | ||||||
| * | | prosodyctl: Move message after condition | Kim Alvefur | 2021-01-21 | 1 | -1/+1 | |
| | | | | | | | | | If the condition is false, the message becomes a lie! | |||||
| * | | util.prosodyctl: Remove unused calculation [luacheck] | Kim Alvefur | 2021-01-21 | 1 | -1/+1 | |
| | | | ||||||
| * | | util.prosodyctl: Rename unused variable to '_' [luacheck] | Kim Alvefur | 2021-01-21 | 1 | -1/+1 | |
| | | | ||||||
| * | | prosodyctl: Fix copypaste oversight | Kim Alvefur | 2021-01-21 | 1 | -2/+2 | |
| | | | ||||||
| * | | util.prosodyctl: Always return exit code from luarocks | Kim Alvefur | 2021-01-21 | 1 | -4/+1 | |
| | | | | | | | | | os.exit(true) errors on Lua 5.1 | |||||
| * | | prosodyctl: Abort if no plugin source specified for the installer | Kim Alvefur | 2021-01-21 | 1 | -1/+7 | |
| | | | | | | | | | Better than having a non-working default. | |||||
| * | | prosodyctl: Move UI related calls out of util.prosodyctl | Kim Alvefur | 2021-01-21 | 2 | -8/+5 | |
| | | | | | | | | | | | I think this follows the general separation of duties between prosodyctl and util.prosodyctl better. | |||||
| * | | prosodyctl: Use luarocks status code as exit code | Kim Alvefur | 2021-01-21 | 1 | -3/+6 | |
| | | | | | | | | | Enables some shell level error handling | |||||
| * | | util.prosodyctl: Reword message to sound more natural | Kim Alvefur | 2021-01-21 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | | English is hard. "to" might also work, but we'll go with this for now. 18:32:11 <MattJ> s/at/in/ ? 18:32:19 <MattJ> to match luarocks :) | |||||
| * | | util.prosodyctl: Propagate status from luarocks invocation | Kim Alvefur | 2021-01-21 | 1 | -1/+6 | |
| | | | ||||||
| * | | util.prosodyctl: Use installer path prepared by util.startup | Kim Alvefur | 2021-01-21 | 1 | -10/+1 | |
| | | | ||||||
| * | | lint: Add initial semgrep config | Kim Alvefur | 2021-01-18 | 1 | -0/+24 | |
| | | | ||||||
| * | | util.datamanager: Fix not passing variables as format string to logger ↵ | Kim Alvefur | 2021-01-16 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | | (thanks semgrep) Passing error messages as format string could lead to errors, although not a problem anymore since util.format sanitizes this. | |||||
| * | | core.modulemanager: Fix resource location compat with LuaRocks 2.x | Kim Alvefur | 2021-01-16 | 1 | -1/+1 | |
| | | | | | | | | | | | The path doesn't include lua version, at least least on Debian, which still has luarocks 2.x | |||||
| * | | MUC: Allow modules to add to the room registration form, and handle the result | Matthew Wild | 2021-01-15 | 1 | -0/+23 | |
| | | | ||||||
| * | | doc/doap.xml: Fix attribute name | Matthew Wild | 2021-01-15 | 1 | -1/+1 | |
| | | | ||||||
| * | | mod_mam: Workaround scansion test flakyness | Kim Alvefur | 2021-01-13 | 1 | -12/+2 | |
| | | | | | | | | | The empty ID fields are sometimes accepted, sometimes not. | |||||
| * | | mod_storage_sql: Fix compatibilty with Lua 5.1 | Kim Alvefur | 2021-01-13 | 1 | -1/+2 | |
| | | | | | | | | | | | | | string.rep() doesn't have the 3rd argument before Lua 5.2 Revert once we drop support for Lua 5.1 | |||||
| * | | mod_muc_mam: Copy extended MAM support from mod_mam | Kim Alvefur | 2021-01-12 | 1 | -4/+21 | |
| | | | | | | | | | | | | | mod_mam and mod_muc_mam are just different enough that having them be the same module gets complicated, but close enough to have overlapping code. | |||||
| * | | mod_mam: Advertise extended MAM when archive storage is capable | Kim Alvefur | 2021-01-12 | 2 | -3/+2 | |
| | | | ||||||
| * | | mod_mam: Allow querying by set of IDs | Kim Alvefur | 2021-01-12 | 1 | -2/+8 | |
| | | | ||||||
| * | | mod_storage_sql: Support query for set of IDs | Kim Alvefur | 2021-01-12 | 1 | -0/+10 | |
| | | | | | | | | | Not compatible with Lua 5.1 | |||||
| * | | mod_storage_internal: Support query for set of IDs | Kim Alvefur | 2021-01-12 | 1 | -0/+8 | |
| | | | | | | | | | Based on implementation in mod_storage_memory | |||||
| * | | mod_storage_memory: Support query for set of IDs | Kim Alvefur | 2021-01-12 | 1 | -0/+8 | |
| | | | ||||||
| * | | storage tests: Add test for querying a set of IDs | Kim Alvefur | 2021-01-12 | 1 | -0/+24 | |
| | | | ||||||
| * | | mod_storage_internal: Add support for full ID range query | Kim Alvefur | 2021-01-12 | 1 | -2/+5 | |
| | | | | | | | | | Based on the mod_storage_memory implementation | |||||
| * | | mod_storage_memory: Support full ID range queries | Kim Alvefur | 2021-01-12 | 1 | -2/+5 | |
| | | | ||||||
| * | | storage tests: Test querys with both before and after IDs | Kim Alvefur | 2021-01-12 | 1 | -0/+21 | |
| | | | | | | | | | Needed for extended MAM, supported by SQL storage already. | |||||
| * | | mod_mam: Add support for before-id and after-id fields | Kim Alvefur | 2021-01-09 | 1 | -4/+9 | |
| | | | ||||||
| * | | mod_storage_sql: Advertise support for id range query | Kim Alvefur | 2021-01-09 | 1 | -0/+1 | |
| | | | | | | | | | That is, a query for items between two IDs (not inclusive). | |||||
 |
index : prosody.git | |
| unofficial mirror of the prosody mercurial project |
| aboutsummaryrefslogtreecommitdiffstats |