Software /
code /
prosody-modules
File
CONTRIBUTING @ 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 | 1809:0b7d65b4f576 |
line wrap: on
line source
Contributing ============ Guidelines for developers ------------------------- - Each module should be contained in a folder of its name (e.g.\ `mod_ping/mod_ping.lua`) - Each module should have a `README.markdown` page in their folder with a description, usage, configuration and todo sections (feel free to copy an existing one as a template) - Commit messages should begin with the name of the plugin they are for (e.g. `mod_ping: Set correct namespace on pongs`) Instructions on cloning the repository are at <https://prosody.im/doc/installing_modules#prosody-modules>