File

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.

---
summary: Collect statistics on rate of log messages
...

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

If you ever wanted to collect statistics on the number of log messages,
this is the module for you!

Setup
=====

After [installing the module](https://prosody.im/doc/installing_modules)
and adding it to modules\_enabled as most other modules, you also need
to add it to your logging config:

``` {.lua}
log = {
  -- your other log sinks
  info = "/var/log/prosody/prosody.log"
  -- add this:
  { to = "measure" };
}
```

Then log messages will be counted by
[statsmanager](https://prosody.im/doc/developers/core/statsmanager).

Compatibility
=============

Reqires Prosody 0.10 or above.