As mentioned in #3854, Let's Encrypt now provides two different chains when acquiring a certificate: one with a cross-signed root certificate (default) and one with a self-signed root certificate.

I'd like to use the alternative chain, which seems to be possible using the preferred_chains option in Caddy. From what I'v

🐣 Is your feature request related to a problem? Please describe.
We had a report in aiohttp-session (see aio-libs/aiohttp-session#574) that a user submitting a 'large' cookie had the cookie dropped by the receiving browser.

According to RFC 6265 - section 6.1:

General-use user agents SHOULD
provide each of the following minimum

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

Currently, we proivde FilteredHttpRequest and FilteredHttpResponse for tranforming a headers or data.
But it is a bit difficult to implement FilteredHttp* because users have to check the type of HttpObject.
Most users might not know the hierarchical relation between HttpOject, HttpHeaders, ResponseHeaders and HttpData

return new FilteredHttpResponse(response) {
      

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.

Currently Attributes only have javadoc; I don't see a major heading on the doc site for them, and googling "http4s attributes" just brings back the api docs for me.

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