Caddy version: v2.2.0 h1:sMUFqTbVIRlmA8NkFnNt9l7s0e+0gw+7GPIrhty905A=

I am trying to pass pem-encoded client certificate to proxied service via a X-SSL-Cert header, like so:

sub.example.com {
    reverse_proxy 127.0.0.1:8000 {
        header_up X-SSL-Cert {http.request.tls.client.certificate_pem}
    }

    tls {
        client_auth {
            mode require
        }
    }
}

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

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

RParser plugins can be selected with the asm.parser eval variable, but there's no way to know which ones are registered, so its not possible to do autocompletion or listings.

Describe the solution you'd like

Do the same as in e asm.arch=?, but for asm.parser

Also i noticed that asm.bits=? is not working either.

Thanks for this amazing tool!

The issue is as following:
If there are two virtual hosts (Server blocks) serving two host names or subdomains:

sd1.domain.com
sd2.domain.com

When the configuration is generated using the nginxconfig and if HTTP to HTTPS redirect is enabled following server block gets generated for each host:

--- For virtual host 1
# HTTP redirect
server {
  

I've following the various docs in an attempt to run Ory Hydra using the binary, and I've used the reference configuration from docs/docs/reference/configuration.md in order to speed up the setup of a basic playground.

On one hand, there seems to be a few outdated values in that reference configuration as per the following warning messages:

{
  "audience": "application",
  "file": "/g

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