I would like to be able to prevent certain headers (Authorization: X-Auth-Token:, etc ) from being included in the caddy logs.

I found caddyserver/caddy#3562, which is asking to be able to set an allowlist of headers, which makes sense for their use case.

In my case, a blocklist, makes more sense, as I only want to prevent a single header from being included in the

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

Work environment

Is your feature request related to a problem? Please describe.

When Hydra receives a request with a token that is no longer valid, it logs an error with what appears to be debug output:

{"debug":"Token is expired","description":"Token expired","error":"token_expired","hint":"The token expired.","level":"error","msg":"An error occurred","time":"2020-08-28T20:14:40Z"}

At high lo

Not exactly a bug, for for those who have been using Claimable in earlier versions of OZ (for the purpose of transferOwnership followed by claimOwnership) - what are the options in v2.0.0?

Relying solely on Ownable.transferOwnership lacks a safety mechanism for accidentally transferring the ownership to an incorrect address.

At present, the only alternative that I see is copying `Cla