The HTTP/2-aware equivalent of Application.

The result of an HTTP2Application; or, alternately, an application that's independent of the request. This is a continuation-passing style function that first provides a response by calling the given respond function, then returns the request's Trailers.

The respond function is similar to the one in Application, but it only takes a streaming body, the status and headers are curried, and it also produces trailers for the stream.

Given to Responders; provide a status, headers, and a stream body, and we'll give you a token proving you called the RespondFunc.

The streaming body of a response. Equivalent to StreamingBody except that it can also write file ranges and return the stream's trailers.

Part of a streaming response -- either a Builder or a range of a file.

Headers sent after the end of a data stream, as defined by section 4.1.2 of the HTTP/1.1 spec (RFC 7230), and section 8.1 of the HTTP/2 spec.

A function given to an HTTP2Application to initiate a server-pushed stream. Its argument is the same as the result of an HTTP2Application, so you can either implement the response inline, or call your own application to create the response.

The result is True if the PUSH_PROMISE frame will be sent, or False if it will not. This can happen if server push is disabled, the concurrency limit of server-initiated streams is reached, or the associated stream has already been closed.

This function shall ensure that stream data provided after it returns will be sent after the PUSH_PROMISE frame, so that servers can implement the requirement that any pushed stream for a resource be initiated before sending DATA frames that reference it.

The synthesized request and headers of a pushed stream.

Create the RequestHeaders corresponding to the given PushPromise.

This is primarily useful for WAI handlers like Warp, and application implementers are unlikely to use it directly.

Promote a normal WAI Application to an HTTP2Application by ignoring the HTTP/2-specific features.

Construct a Responder that will just call the RespondFunc with the given arguments.

Fold the ContT into the contained Responder.

Fold the IO into the contained Responder.

Serve the requested range of the specified file (based on the Range header), using the given Status and ResponseHeaders as a base. If the file is not accessible, the status will be replaced with 404 and a default not-found message will be served. If a partial file is requested, the status will be replaced with 206 and the Content-Range header will be added. The Content-Length header will always be added.

Respond with a single range of a file, adding the Accept-Ranges, Content-Length and Content-Range headers and changing the status to 206 as appropriate.

If you want the range to be inferred automatically from the Range header, use respondFile instead. On the other hand, if you want to avoid the automatic header and status adjustments, use respond and streamFilePart directly.

Respond with a minimal 404 page with the given headers.

Fold the given bracketing action into a Responder. Note the first argument is isomorphic to Codensity IO a or forall s. ContT s IO a, and is the type of a partially-applied bracket or with-style function.

respondWith (bracket acquire release) $
    \x -> respondNotFound [("x", show x)]

is equivalent to

Responder $ \k -> bracket acquire release $
    \x -> runResponder (respondNotFound [("x", show x)] k

This is morally equivalent to (>>=) on Codensity IO.

Create a response body consisting of a single range of a file. Does not set Content-Length or Content-Range headers. For that, use respondFilePart or respondFile.

Create a response body consisting of a single builder.

Create a response body of a stream of Builders.