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
        }
    }
}

If you're using proxies with requests-html and rendering JS sites is all good. Once you render a website pyppeteer don't know about this proxies and will expose your IP. This is an undesired behavior when scraping with proxies.

The idea is that whenever someone passes in proxies to the session object or any method call, make pyppeteer also use these proxies. #265

The library has many constant definitions that are declared as NAME = 'val', e.g. https://github.com/aio-libs/aiohttp/blob/master/aiohttp/client.py#L161

We need to add Final type hint to let users know that these constants should be considered as immutable (this hint doesn't prevent the actual modification and fully backward compatible).

from typing_extensions import Final  # suppor

As we attempt to pick up the release cadence, we are in need of an explicit changelog file which enumerates changes in each version. This should be a markdown or plaintext file adhering to some form of standardized format. Ideally, it will be able to work with #582.

The example nginx configuration in the Deploying Falcon on Linux with NGINX and uWSGI article could probably be improved to include https configuration and redirect of http to https, since I believe it's the most common configuration now.

Maybe we could use a configuration from this great [Mozilla site](https://ssl-config