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

Hello!

I've noticed, that aiohttp is simply concatenating server-response (or client-request) header like this, w/o any validation:

    line = status_line + '\r\n' + ''.join(
        [k + ': ' + v + '\r\n' for k, v in headers.items()])

Which may be not okay, if some of the header values were based on user input.

Consider this example:

import aiohttp.web
asyn

The docs do not give a format option for iso date with microseconds. Is this possible?

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

This is probably a scalafmt setting we can tweak. It will be valid Scala 2, so we should do this on series/0.21.

[error] -- Error: /home/ross/src/http4s/core/src/main/scala/org/http4s/metrics/MetricsOps.scala:97:58 
[error] 97 |  ): Request[F] => Option[String] = { request: Request[F] =>
[error]    |                                                          ^
[error]    |           pare

Hi, when implementing http4k/http4k#435 I noticed the codebase does not have a linter set up - e.g. some files end with new lines and some don't.

I am not sure whether this is desired, I would be happy to participate if wanted.