Mercurial > prosody-modules
view mod_http_debug/README.md @ 6319:04c3273cb81f
mod_auth_cyrus: Add empty 'profile' table to SASL handler objects
This is for compatibility with Prosody's built-in util.sasl objects.
A SASL profile table usually includes methods supported by the backend, which
can be used by SASL mechanism handlers to perform operations (such as testing
the password). It also optionally contains a 'cb' field with channel binding
method handlers.
The Cyrus backend doesn't support channel binding, and doesn't have the same
concept of auth backend methods (it handles all that internally, and Prosody
has no insight or control over it).
Thus, we create an empty profile which informs Prosody that the SASL handler
does not support any of the auth or channel binding methods. Some features
will not work, but they didn't work anyway. This just makes it explicit.
This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to
always contain a 'profile' field.
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Thu, 04 Sep 2025 10:14:46 +0100 |
| parents | 91564b57e595 |
| children |
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" }; ```
