HORIZON HASKELLDocslts/ghc-9.14.xb2f3bfd2026-10-11Search names, modules, packages, or :: a typeCtrl K

GHC 9.14.1 · lts/ghc-9.14.x · b2f3bfd · 2026-10-11

Modulehttp2-5.4.8Haskell2010

Network.HTTP2.Server

HTTP/2 server library.

Example:

{-# LANGUAGE OverloadedStrings #-}
module Main (main) where

import qualified Control.Exception as E
import Data.ByteString.Builder (byteString)
import Network.HTTP.Types (ok200)
import Network.Run.TCP (runTCPServer) -- network-run

import Network.HTTP2.Server

main :: IO ()
main = runTCPServer Nothing "80" runHTTP2Server
  where
    runHTTP2Server s = E.bracket (allocSimpleConfig s 4096)
                                 freeSimpleConfig
                                 (\config -> run defaultServerConfig config server)
    server _req _aux sendResponse = sendResponse response []
      where
        response = responseBuilder ok200 header body
        header = [("Content-Type", "text/plain")]
        body = byteString "Hello, world!\n"
  • 21 types
  • 55 values
  • Packagehttp2-5.4.8
  • Exports76
  • LanguageHaskell2010
  • LicenceBSD-3-Clause
  • SourceServer.hs

Runner

1 declaration

Server configuration

5 declarations

The default server config.

Example1 expression
defaultServerConfigServerConfig {numberOfWorkers = 8, connectionWindowSize = 16777216, settings = Settings {headerTableSize = 4096, enablePush = True, maxConcurrentStreams = Just 64, initialWindowSize = 262144, maxFrameSize = 16384, maxHeaderListSize = Nothing, pingRateLimit = 10, emptyFrameRateLimit = 4, settingsRateLimit = 4, rstRateLimit = 4}}

HTTP/2 setting

8 declarations

The default settings.

Example1 expression
defaultSettingsSettings {headerTableSize = 4096, enablePush = True, maxConcurrentStreams = Just 64, initialWindowSize = 262144, maxFrameSize = 16384, maxHeaderListSize = Nothing, pingRateLimit = 10, emptyFrameRateLimit = 4, settingsRateLimit = 4, rstRateLimit = 4}

Rate limits

valuerstRateLimit :: Settings -> Int
#

Maximum number of streams reset per second, whether by the peer's RST_STREAM (CVE-2023-44487) or by ours in answer to a stream error the peer caused (CVE-2025-8671)

Common configuration

58 declarations
datadata Config
#

HTTP/2 configuration.

valuedefaultConfig :: Config
#

Default config. This is just a template to modify via field names. Don't use this without modifications.

The size of the write buffer. We assume that the read buffer is the same size. So, this value is announced via SETTINGS_MAX_FRAME_SIZE to the peer.

Making simple configuration whose IO is not efficient. A write buffer is allocated internally. WAI timeout manger is initialized with 30_000_000 microseconds.

Making simple configuration whose IO is not efficient. A write buffer is allocated internally. The third argument is microseconds to initialize WAI timeout manager.

valuefreeSimpleConfig :: Config -> IO ()
#

Deallocating the resource of the simple configuration.

This does not cancel timeout actions registered with confTimeoutManager. Since time-manager 0.3, a manager holds no registrations, so there is nothing to kill: an action registered with register runs even after this returns unless it is cancelled with cancel. Use withHandle, which cancels it when the scope ends.

Naive implementation for readN.

NOTE: This function is intended to be used by a single thread only. (It is probably quite rare anyway to want concurrent reads from the same network socket.)

datadata Sentinel
#

Constructors

  • Closer (IO ())

    Closing a file resource. Its refresher is automatiaclly generated by the internal timer.

  • Refresher (IO ())

    Refreshing a file resource while reading. Closing the file must be done by its own timer or something.

typetype Server = Request -> Aux -> (Response -> [PushPromise] -> IO ()) -> IO ()
#

Server type. Server takes a HTTP request, should generate a HTTP response and push promises, then should give them to the sending function. The sending function would throw exceptions so that they can be logged.

The sending function must only be called once.

datadata Aux
#

Additional information.

Send an informational (1xx) response, e.g. 103 Early Hints, on this request's stream before the final response. May be called multiple times. A no-op in defaultAux.

newtypenewtype Request
#

Request from client.

Instances1Show
  • Show RequestDefined in http-semantics-0.4.1 · Network.HTTP.Semantics.Server.Internal
newtypenewtype Response
#

Response from server.

Instances1Show
  • Show ResponseDefined in http-semantics-0.4.1 · Network.HTTP.Semantics.Server.Internal

Trailers maker. A chunks of the response body is passed with Just. The maker should update internal state with the ByteString and return the next trailers maker. When response body reaches its end, Nothing is passed and the maker should generate trailers. An example:

{-# LANGUAGE BangPatterns #-}
import Data.ByteString (ByteString)
import qualified Data.ByteString.Char8 as C8
import Crypto.Hash (Context, SHA1) -- cryptonite
import qualified Crypto.Hash as CH

-- Strictness is important for Context.
trailersMaker :: Context SHA1 -> Maybe ByteString -> IO NextTrailersMaker
trailersMaker ctx Nothing = return $ Trailers [("X-SHA1", sha1)]
  where
    !sha1 = C8.pack $ show $ CH.hashFinalize ctx
trailersMaker ctx (Just bs) = return $ NextTrailersMaker $ trailersMaker ctx'
  where
    !ctx' = CH.hashUpdate ctx bs

Usage example:

let h2rsp = responseFile ...
    maker = trailersMaker (CH.hashInit :: Context SHA1)
    h2rsp' = setResponseTrailersMaker h2rsp maker
datadata OutBodyIface
#

Constructors

  • OutBodyIface
    • outBodyUnmask :: forall x. IO x -> IO x

      Unmask exceptions in the thread spawned for the request body

      This is used in the client: we spawn the new thread for the request body with exceptions masked, and provide the body of OutBodyStreamingIface with a callback to unmask them again (typically after installing an exception handler).

      Unmasking in the server is a no-op, as here the scope of the thread that is spawned for the server is the entire handler, not just the response streaming body.

    • outBodyPush :: Builder -> IO ()

      Push a new chunk

      In http2, there is no direct correspondence between chunks and the resulting DATA frames sent: the chunks are collected (written to an internal write buffer) until we can fill a frame.

      See also outBodyFlush.

    • outBodyPushFinal :: Builder -> IO ()

      Push the final chunk

      Using this function instead of outBodyPush can be used to guarantee that the final HTTP2 DATA frame is marked end-of-stream; with outBodyPush it may happen that an additional empty DATA frame is used for this purpose. Additionally, after calling this function, outBodyCancel will be a no-op.

    • outBodyCancel :: Maybe SomeException -> IO ()

      Cancel the stream

      Sends a RST_STREAM to the peer. If cancelling as the result of an exception, a Just should be provided which specifies the exception which will be stored locally as the reason for cancelling the stream; in this case, the error code sent with the RST_STREAM will be INTERNAL_ERROR (see https://datatracker.ietf.org/doc/html/rfc7540#section-7). If Nothing is given, the error code will be CANCEL.

      If there is a partially constructed DATA frame at the time of cancellation, this frame is discarded. If this is undesirable, you should call outBodyFlush prior to cancelling.

    • outBodyFlush :: IO ()

      Flush

      This can be used to emit a DATA frame with the data collected so far (using outBodyPush), even if that DATA frame has not yet reached the maximum frame size. Calling outBodyFlush unnecessarily can therefore result in excessive overhead from frame headers.

      If no data is available to send, this is a no-op.