Software /
code /
prosody-modules
File
mod_map/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 | 3653:d31fa28d9482 |
line wrap: on
line source
--- labels: - 'Stage-Experimental' summary: Prototype MAM summary --- This is a prototype for an experimental archive summary API recently added in [Prosody trunk](https://hg.prosody.im/trunk/rev/2c5546cc5c70). # Protocol ::: {.alert .alert-danger} This is not a finished protocol, but a prototype meant for testing. ::: A basic query: ``` {.xml} <iq id="lx7" type="get"> <summary xmlns="xmpp:prosody.im/mod_map"/> </iq> ``` Answered like: ``` {.xml} <iq type="result" id="lx7"> <summary xmlns="xmpp:prosody.im/mod_map"> <item jid="juliet@capulet.lit"> <count>3</count> <start>2019-02-25T15:48:00+0100</start> <end>2019-08-23T01:39:50+02:00</end> <body>O Romeo, Romeo! wherefore art thou Romeo?</body> </item> </summary> </iq> ``` It can also take dataform and RSM parameters similar to a [filtered MAM query](https://xmpp.org/extensions/xep-0313.html#filter). E.g if the last message you received had an id `09af3-cc343-b409f` then the following query would tell you who sent you messages since: ``` {.xml} <iq id="lx8" type="get"> <summary xmlns="xmpp:prosody.im/mod_map"> <set xmlns="http://jabber.org/protocol/rsm"> <max>10</max> <after>09af3-cc343-b409f</after> </set> </summary> </iq> ```