http-server

I have modified the default file_server browse template to integrate it with a website, by using httpInclude to load blocks of HTML containing the header, footer and theme. These files are hosted on the same Caddy instance, and it works well provided that compression is not enabled. When compression is enabled, the file_server browser becomes garbage: it appears that raw compressed data is inc

🐞 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?

Could you make HttpResponse capable of sending part of file by Range header, or by user specified offset and size ?

The TcpConnection class do have a public sendFile method with offset and length parameters, but HttpResponse can not take any advantages of that. Currently it can only send the whole file at one time. Maybe a setRange method would be enough?

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

If a user performs a blocking task in decorator chains or services, they have to 1) submit a task to a blocking task executor,
2) pass the result to a CompletableFuture and 3) wrap the CompletableFuture with HttpResponse.from().

sb.serviceUnder("/web", service.decorate((delegate, ctx, req) -> {
    CompletableFuture<HttpResponse> future = new CompletableFuture<>();
    ctx.bl

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)

Not really a bug or feature request per se, just a deprecation notice. Regarding these:

https://github.com/tinyhttp/tinyhttp/blob/94875e2c334c09143a849f529e028b7a6c22a18e/packages/app/src/request.ts#L16-L28

https://github.com/tinyhttp/tinyhttp/blob/94875e2c334c09143a849f529e028b7a6c22a18e/packages/app/src/request.ts#L33-L34

req.connection is deprecated. https://nodejs.org/api/http.html#

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