http-server

Hi,

I am running Caddy v2.4.3 on FreeBSD 12.2

I have an entry in my Caddyfile that looks like this (obviously the domain names and the Cloudflare key have been substituted with placeholder values here, but other than that I am showing exactly what I have):

api.example.com {
    reverse_proxy {
        to 10.13.37.7 unix//var/www/com.example.api/example-http-api/run/public.sock

Describe the bug

Originally, @asvetlov intended to delete any use of attrs from aiohttp 4.0+ series via aio-libs/aiohttp#5284. He dropped it from the runtime deps too.

But there are some places that still rely on attrs meaning that this will cause failures in runtime because of the missing dep. The tests currently succeed because attrs is listed as a test dep.

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

For the database layer, I am currently weighing up ODB, Oat++, SOCI, cppdb, and sqlpp11 [if sqlpp adds support for CREATE TABLE]. You here at drogon seem to have your own [ORM](https://en.wikipedia.

Ref: #214

After reviewing the source for the send method, it seems that the function is not designed to be used in any place except the tail end of the middleware stack, since it throws (an HttpError with status 404) when there is no match.

This seems rather opinionated (which is fine), but it was not very intuitive for me, and I think it needs to be documented.

It would be nice to

When writing a test case with ServerRule or ServerExtension, a user sometimes wants to capture the ServiceRequestContexts:

class MyJUnit5Test {
  static final var serviceContexts =
      new LinkedBlockingQueue<ServiceRequestContext>();

  @RegisterExtension
  static final var server = new ServerExtension() {
    @Override
    protected void configure(ServerBuilder sb) thr

Might be a cool feature to show a symlinks destination path behind the little arrow. This would be a bit like the listing of ls -l.

Hi in the past BlazeClientConfig had some documentation on the configurables:
https://http4s.org/v0.20/api/org/http4s/client/blaze/blazeclientconfig

These were super helpful for teams using this library as it gave insight into the inner workings of the client without having to do a full dive into the codebase.

Seems like the documentation was not included when moving to `BlazeClientBuilde

The OpenApi specification allows top-level servers object to be specified:

Field Name	Type	Description
servers	[Server Object]	An array of Server Objects, which provide connectivity information to a target server. If the servers

Now that @tinyhttp/router v1.0.5+ no longer depends on http module of Node.js, it should be very easy to implement basic Deno support for tinyhttp. Probably it would be cool to have it located in the separate deno folder with all editor settings specifically for it.

There aren't strict requirements on how it should be implemented, but i suppose we need to use either raw gh links, jspm or