http-server

It seems Caddy does not support wildcards/ expression matching in the reverse proxy's header_up.

For example this does not remove any headers:

header_up -X-SHIBBOLETH-*

This works as expected, but is limited in its use:

header_up -X-SHIBBOLETH-LOGIN

It'd be great if Caddy would support wildcards/ expression matching in the reverse proxy's header_up/ header_down.

🐞 Describe the bug

TraceConfig.on_response_chunk_received doesn't trace if the response body is read from ClientResponse.content

This behavior isn't obvious when looking at Tracing Reference, [Streaming Response Content](https://docs.aiohttp.org/e

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.

Hello there! After some experimentation with the mocking API, I discovered that mocked contexts do not provide a mocked Cookies instance. Suppose we wanted to test the following middleware:

// session.ts
// Explicit type annotations omitted for brevity...
export function checkSession(ctx) {
    const maybeSessionId = ctx.cookies.get('sid');
    ctx.assert(maybeSessionId, St

Just a suggestion.

I feel like Armeria's CookieBuilder makes it too easy to create an insecure service. Default of secure, http only, same site cookies and requiring a user to explicitly opt out would help prevent accidental cookie leaks without a real UX penalty when the use case does need something more lax.

actix-web has a ready-to-go compress middleware. I currently don't really see any downsides with turning that on. Will have to do a little benchmarking to see whether it's ok to generally turn this on.

We sometimes have data types which subtype Ordered and other times have types which implement Ordering. We only need to do Ordering. We should ensure that all types which are Ordered also have an Ordering instance.

Context: http4s/http4s#5013 (comment)

Describe the bug

When an optional route param (i.e. /foo/:bar?) is not supplied for a particular request, the req.params object will still contain it, with a string value of "undefined".

This would mean that i.e. if (req.params.bar) would unexpectedly always be truthy, even when the param was not supplied.

To Reproduce

Simple app with optional route param bar:

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