I would like to be able to prevent certain headers (Authorization: X-Auth-Token:, etc ) from being included in the caddy logs.

I found caddyserver/caddy#3562, which is asking to be able to set an allowlist of headers, which makes sense for their use case.

In my case, a blocklist, makes more sense, as I only want to prevent a single header from being included in the

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

Discoverabilith of middleware is not as good as it could be. We can create a middlewares page on the site documenting what we have available as well as a community section at the bottom where others can list their middlewares since a lot of our features come from middleware.

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.