Software /
code /
prosody-modules
File
mod_http_debug/README.md @ 6113:c0cb43817b7c
mod_compliance_latest: using module:log_status
diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua
--- a/mod_compliance_latest/mod_compliance_latest.lua
+++ b/mod_compliance_latest/mod_compliance_latest.lua
@@ -1,6 +1,6 @@
local success, err = pcall(function() module:depends("compliance_2023") end)
if not success then
- module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?")
- return 1, "Error: Couldn't load dependency mod_compliance_2023."
+module:log_status( "error", "Error, can't load module: mod_compliance_2023. Is this module downloaded into a folder readable by prosody?" )
+return false
end
author | Menel <menel@snikket.de> |
---|---|
date | Mon, 23 Dec 2024 14:09:56 +0100 |
parent | 5490:91564b57e595 |
line wrap: on
line source
--- summary: HTTP module returning info about requests for debugging --- This module returns some info about HTTP requests as Prosody sees them from an endpoint like `http://xmpp.example.net:5281/debug`. This can be used to validate [reverse-proxy configuration][doc:http] and similar use cases. # Example ``` $ curl -sSf https://xmpp.example.net:5281/debug | json_pp { "body" : "", "headers" : { "accept" : "*/*", "host" : "xmpp.example.net:5281", "user_agent" : "curl/7.74.0" }, "httpversion" : "1.1", "id" : "jmFROQKoduU3", "ip" : "127.0.0.1", "method" : "GET", "path" : "/debug", "secure" : true, "url" : { "path" : "/debug" } } ``` # Configuration HTTP Methods handled can be configured via the `http_debug_methods` setting. By default, the most common methods are already enabled. ```lua http_debug_methods = { "GET"; "HEAD"; "DELETE"; "OPTIONS"; "PATCH"; "POST"; "PUT" }; ```