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

C:\projects\radare2\shlr\tree-sitter\lib\src\alloc.h(57,21): warning C4477: 'fprintf' : format string '%lu' requires an argument of ty

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

AWS Fargate and ECS is a popular container cluster. Jaeger and datadog are not native to AWS, require additional setup, cost and operations. AWS X-Ray support distributed tracing for ECS and AWS lambda. A custom lambda can be developed for oauth2 token validation against Hydra. Currently tracing between lambda authorizer and hyd

🧐 Motivation
Create simple ERC20 and ERC777 presets with fixed supply.
The benefits are:

• Easy to deploy (including from Remix).
• No access control (for minting/pausing), and hence no governance required.
• Can be verified easily on public networks and then are verified for all.

📝 Details

Community members are creating their own simple ERC20 tokens, so it would be good if they