http-client-overrides: HTTP client overrides

[ bsd3, library, network, program ] [ Propose Tags ]

A library for applying overrides to ManagerSettings when using the http-client library.

[Skip to Readme]


Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


Versions [RSS],
Dependencies aeson (>=, base (>=4.7 && <5), bytestring (>=, http-client (>=0.5.5), http-client-overrides, http-client-tls, http-types (>=0.7.0), network-uri (>=, text (>=0.3), yaml (>=0.8.11) [details]
License BSD-3-Clause
Copyright 2019 Robbie McMichael
Author Robbie McMichael
Maintainer Robbie McMichael
Category Network
Home page
Source repo head: git clone
Uploaded by robbiemcmichael at 2019-10-02T01:05:30Z
Distributions LTSHaskell:, NixOS:, Stackage:
Executables example
Downloads 1104 total (7 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2019-10-02 [all 1 reports]

Readme for http-client-overrides-

[back to package description]


A library for applying overrides to ManagerSettings when using the http-client Haskell library.


You probably have some IO do notation hidden somewhere which looks like this:

manager <- newManager tlsManagerSettings

Replace it with this:

settings <- withHttpClientOverridesThrow tlsManagerSettings
manager  <- newManager settings

Set the HTTP_CLIENT_OVERRIDES environment variable to the location of your configuration file. When this environment variable is not set there is no additional overhead for HTTP requests as the ManagerSettings will not be modified. Refer to the example directory for a sample Haskell program and configuration file.


Log HTTP requests and responses

The following fields can be used to print log messages for all HTTP responses, requests and request overrides:

version: v1
  responses: simple
  requests: simple
  requestOverrides: simple

The currently supported log formats are simple and detailed. Sample output for the simple log format is shown below:

Overriding request: https://unreachable.domain/ ->
Request: GET HTTP/1.1
Response: HTTP/1.1 200 OK

Override HTTP requests

Match HTTP requests corresponding to a match URL and transform the request according to an override URL:

version: v1
- match: unreachable.domain

Match semantics

Matches the first HTTP request which:

  • has the same scheme, host and port as the match URL
  • has a path which is a suffix of the path in the match URL

Any URL segments ommitted from the match URL are not required for matching.

Override semantics

Overrides an HTTP request with:

  • the scheme, host and port specified in the override URL
  • replaces the prefix of a matched path with the path in the override URL

Any URL segments ommitted from the override URL will not be applied to the HTTP request.


Override all HTTP requests on port 80 to use HTTPS on port 443 (note: the port is never automatically interpreted from the scheme):

version: v1
- match: http://:80
  override: https://:443

Override all requests to the host which have a path prefix of /dhall-lang/dhall-lang/ to use a path prefix of /robbiemcmichael/dhall-lang/ instead.

version: v1
- match:


Set logOptions.requestOverrides to detailed to see how the URLs have been parsed and how any matched HTTP requests are being overridden.