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.

local bytes = module:measure("bytes", "sizes");
local lines = module:measure("lines", "distribution");
local words = module:measure("words", "distribution");

local function measure_length(event)
	local body = event.stanza:get_child_text("body");
	if body then
		bytes(#body);
		lines(select(2, body:gsub("[^\n]+","")));
		words(select(2, body:gsub("%S+","")));
	end
end

module:hook("message/full", measure_length);
module:hook("message/bare", measure_length);
module:hook("message/host", measure_length);

module:hook("pre-message/full", measure_length);
module:hook("pre-message/bare", measure_length);
module:hook("pre-message/host", measure_length);