File

mod_stanza_counter/README.markdown @ 5705:527c747711f3

mod_http_oauth2: Limit revocation to clients own tokens in strict mode RFC 7009 section 2.1 states: > The authorization server first validates the client credentials (in > case of a confidential client) and then verifies whether the token was > issued to the client making the revocation request. If this > validation fails, the request is refused and the client is informed of > the error by the authorization server as described below. The first part was already covered (in strict mode). This adds the later part using the hash of client_id recorded in 0860497152af It still seems weird to me that revoking a leaked token should not be allowed whoever might have discovered it, as that seems the responsible thing to do.
author Kim Alvefur <zash@zash.se>
date Sun, 29 Oct 2023 11:30:49 +0100
parent 1803:4d73a1a6ba68
line wrap: on
line source

---
labels:
- 'Stage-Stable'
summary: Simple incoming and outgoing stanza counter
...

Introduction
============

This module counts incoming and outgoing stanzas from when the instance
started, and makes the data available to other modules by creating a
global prosody. object

Details
=======

The counter module is "stanza\_counter", the example output module is
stanza\_counter\_http.

Usage
=====

Copy both files into prosody's module directory and place 'em into your
enabled modules (stanza\_counter\_http requires to be loaded into the
global section!)

Config for stanza\_counter\_http:

``` {.lua}

stanza_counter_basepath = "/counter-path-custom/"
```

Info
====

-   As of now to count components stanzas, it needs to be manually
    loaded (inserted into modules\_enabled of the components' sections)
    on these.
-   This version isn't compatible with previous versions of prosody
    (looks at 0.8-diverge branch for olders).