https://github.com/caddyserver/caddy/blob/3ee663dee195e5f8ead7879b31131f46cd0fba13/modules/caddyhttp/reverseproxy/reverseproxy.go#L644-L653

As discussed on Reddit, it seems that reverse proxying some applications (in this case Plex) can lead to some extensive error log spamming. Requ

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

Login and consent challenges time out, but I haven't found a way to determine if this has happened

After being redirected to the login and consent pages, you're given a login/consent challenge. After the user has somehow authenticated himself, the login/consent session is accepted to hydra with the given login/consent challenge. However, if this takes too long (I believe it's a 10 minute ti

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