Mercurial > prosody-modules
view mod_component_http/README.md @ 6082:1a6cd0bbb7ab
mod_compliance_2023: Add 2023 Version of the compliance module, basis is the 2021 Version.
diff --git a/mod_compliance_2023/README.md b/mod_compliance_2023/README.md
new file mode 100644
--- /dev/null
+++ b/mod_compliance_2023/README.md
@@ -0,0 +1,22 @@
+---
+summary: XMPP Compliance Suites 2023 self-test
+labels:
+- Stage-Beta
+rockspec:
+ dependencies:
+ - mod_cloud_notify
+
+...
+
+Compare the list of enabled modules with
+[XEP-0479: XMPP Compliance Suites 2023] and produce basic report to the
+Prosody log file.
+
+If installed with the Prosody plugin installer then all modules needed for a green checkmark should be included. (With prosody 0.12 only [mod_cloud_notify] is not included with prosody and we need the community module)
+
+# Compatibility
+
+ Prosody-Version Status
+ --------------- ----------------------
+ trunk Works as of 2024-12-21
+ 0.12 Works
diff --git a/mod_compliance_2023/mod_compliance_2023.lua b/mod_compliance_2023/mod_compliance_2023.lua
new file mode 100644
--- /dev/null
+++ b/mod_compliance_2023/mod_compliance_2023.lua
@@ -0,0 +1,79 @@
+-- Copyright (c) 2021 Kim Alvefur
+--
+-- This module is MIT licensed.
+
+local hostmanager = require "core.hostmanager";
+
+local array = require "util.array";
+local set = require "util.set";
+
+local modules_enabled = module:get_option_inherited_set("modules_enabled");
+
+for host in pairs(hostmanager.get_children(module.host)) do
+ local component = module:context(host):get_option_string("component_module");
+ if component then
+ modules_enabled:add(component);
+ modules_enabled:include(module:context(host):get_option_set("modules_enabled", {}));
+ end
+end
+
+local function check(suggested, alternate, ...)
+ if set.intersection(modules_enabled, set.new({suggested; alternate; ...})):empty() then return suggested; end
+ return false;
+end
+
+local compliance = {
+ array {"Server"; check("tls"); check("disco")};
+
+ array {"Advanced Server"; check("pep", "pep_simple")};
+
+ array {"Web"; check("bosh"); check("websocket")};
+
+ -- No Server requirements for Advanced Web
+
+ array {"IM"; check("vcard_legacy", "vcard"); check("carbons"); check("http_file_share", "http_upload")};
+
+ array {
+ "Advanced IM";
+ check("vcard_legacy", "vcard");
+ check("blocklist");
+ check("muc");
+ check("private");
+ check("smacks");
+ check("mam");
+ check("bookmarks");
+ };
+
+ array {"Mobile"; check("smacks"); check("csi_simple", "csi_battery_saver")};
+
+ array {"Advanced Mobile"; check("cloud_notify")};
+
+ array {"A/V Calling"; check("turn_external", "external_services", "turncredentials", "extdisco")};
+
+};
+
+function check_compliance()
+ local compliant = true;
+ for _, suite in ipairs(compliance) do
+ local section = suite:pop(1);
+ if module:get_option_boolean("compliance_" .. section:lower():gsub("%A", "_"), true) then
+ local missing = set.new(suite:filter(function(m) return type(m) == "string" end):map(function(m) return "mod_" .. m end));
+ if suite[1] then
+ if compliant then
+ compliant = false;
+ module:log("warn", "Missing some modules for XMPP Compliance 2023");
+ end
+ module:log("info", "%s Compliance: %s", section, missing);
+ end
+ end
+ end
+
+ if compliant then module:log("info", "XMPP Compliance 2023: Compliant ✔️"); end
+end
+
+if prosody.start_time then
+ check_compliance()
+else
+ module:hook_global("server-started", check_compliance);
+end
+
| author | Menel <menel@snikket.de> |
|---|---|
| date | Sun, 22 Dec 2024 16:06:28 +0100 |
| parents | fe081789f7b5 |
| children |
line wrap: on
line source
--- summary: 'Allows implementing a component or bot over HTTP' ... Introduction ============ This module allows you to implement a component that speaks HTTP. Stanzas (such as messages) coming from XMPP are sent to a configurable URL as a HTTP POST. If the POST returns a response, that response is returned to the sender over XMPP. See also mod_post_msg. Example usage ------------- Example echo bot in PHP: ``` php <?php // Receive and decode message JSON $post_data = file_get_contents('php://input'); $received = json_decode($post_data)->body; // Send response header('Content-Type: application/json'); echo json_encode(array( 'body' => "Did you say $received?" )); ?> ``` Configuration ============= The module is quite flexible, but should generally be loaded as a component like this: ``` Component "yourservice.example.com" "component_http" component_post_url = "https://example.com/your-api" ``` Such a component would handle traffic for all JIDs with 'yourservice.example.com' as the hostname, such as 'foobar@yourservice.example.com'. Although this example uses a subdomain, there is no requirement for the component to use a subdomain. Available configuration options are: Option Description ------------------------------------ ------------------------------------------------------------------------------------------------------------------------------------------------- component\_post\_url The URL that will handle incoming stanzas component\_post\_stanzas A list of stanza types to forward over HTTP. Defaults to `{ "message" }`. Details ======= Requests -------- Each received stanza is converted into a JSON object, and submitted to `component_post_url` using a HTTP POST request. The JSON object always has the following properties: Property Description -------------------------- ------------ to The JID that the stanza was sent to (e.g. foobar@your.component.domain) from The sender's JID. kind The kind of stanza (will always be "message", "presence" or "iq". stanza The full XML of the stanza. Additionally, the JSON object may contain the following properties: Property Description -------------------------- ------------ body If the stanza is a message, and it contains a body, this is the string content of the body. Responses --------- If you wish to respond to a stanza, you may include a reply when you respond to the HTTP request. Responses must have a HTTP status 200 (OK), and must set the Conent-Type header to `application/json`. A response may contain any of the properties of a request. If not supplied, then defaults are chosen. If 'to' and 'from' are not specified in the response, they are automatically swapped so that the reply is sent to the original sender of the stanza. If 'kind' is not set, it defaults to 'message', and if 'body' is set, this is automatically added as a message body. If 'stanza' is set, it overrides all of the above, and the supplied stanza is sent as-is using Prosody's normal routing rules. Note that stanzas sent by components must have a 'to' and 'from'. Presence -------- By default the module automatically handles presence to provide an always-on component, that automatically accepts subscription requests. This means that by default presence stanzas are not forwarded to the configured URL. To provide your own presence handling, you can override this by adding "presence" to the component\_post\_stanzas option in your config. Compatibility ============= Should work with all versions of Prosody from 0.9 upwards.
