Software /
code /
prosody-modules
File
mod_debug_traceback/README.markdown @ 5185:09d6bbd6c8a4
mod_http_oauth2: Fix treatment of 'redirect_uri' parameter in code flow
It's optional and the one stored in the client registration should
really be used instead. RFC 6749 says an URI provided as parameter MUST
be validated against the stored one but does not say how.
Given that the client needs their secret to proceed, it seems fine to
leave this for later.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 02 Mar 2023 22:00:42 +0100 |
parent | 4214:5841d54cb6c6 |
child | 5874:0358fcf14cd6 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Generate tracebacks on-demand --- # Introduction This module writes out a traceback to a file when a chosen signal (by default `SIGUSR1`) is received. It can be useful to diagnose cases where Prosody is unresponsive. # Configuration `debug_traceback_filename` : The name of the file to write the traceback to. Some variables are supported, see [mod_log_ringbuffer] docs for more info. Defaults to `{paths.data}/traceback-{pid}-{count}.log`. `debug_traceback_signal` : The name of the signal to listen for. Defaults to `SIGUSR1`. # Compatibility Prosody 0.11 or later.