Http is:module

Support for HTTP response encoding.

The HTTP module provides a simple interface for sending and receiving content over HTTP in Haskell. Here's how to fetch a document from a URL and return it as a String:

simpleHTTP (getRequest "http://www.haskell.org/") >>= fmap (take 100) . getResponseBody
-- fetch document and return it (as a 'String'.)

Other functions let you control the submission and transfer of HTTP Requests and Responses more carefully, letting you integrate the use of HTTP functionality into your application. The module also exports the main types of the package, Request and Response, along with Header and functions for working with these. The actual functionality is implemented by modules in the Network.HTTP.* namespace, letting you either use the default implementation here by importing Network.HTTP or, for more specific uses, selectively import the modules in Network.HTTP.*. To wit, more than one kind of representation of the bulk data that flows across a HTTP connection is supported. (see Network.HTTP.HandleStream.) NOTE: The Request send actions will normalize the Request prior to transmission. Normalization such as having the request path be in the expected form and, possibly, introduce a default Host: header if one isn't already present. Normalization also takes the "user:pass@" portion out of the the URI, if it was supplied, and converts it into Authorization: Basic$ header. If you do not want the requests tampered with, but sent as-is, please import and use the the Network.HTTP.HandleStream or Network.HTTP.Stream modules instead. They export the same functions, but leaves construction and any normalization of Request@s to the user. NOTE: This package only supports HTTP; it does not support HTTPS. Attempts to use HTTPS result in an error.

Here is an example GET request that streams the response body to standard output:

import Pipes
import Pipes.HTTP
import qualified Pipes.ByteString as PB  -- from `pipes-bytestring`

main = do
req <- parseUrlThrow "https://www.example.com"

manager <- withManager tlsManagerSettings

withHTTP req manager $ \resp ->
runEffect $ responseBody resp >-> PB.stdout

Here is an example POST request that also streams the request body from standard input:

{-# LANGUAGE OverloadedStrings #-}

import Pipes
import Pipes.HTTP
import qualified Pipes.ByteString as PB

main = do
req <- parseUrlThrow "https://www.example.com"

let req' = req
{ method = "POST"
, requestBody = stream PB.stdin
}

manager <- newManager tlsManagerSettings

withHTTP req' manager $ \resp ->
runEffect $ responseBody resp >-> PB.stdout

For non-streaming request bodies, study the RequestBody type, which also accepts strict / lazy bytestrings or builders.

Implementation of HttpLib using cabal-install's own HttpTransport

libcurl input

A layer on top of the HTTP functions in the http-client library which lifts the return values to the typeclasses we are using in this library. Non 200 responses are converted into MonadError errors.

Implementation of HttpClient using the HTTP package

Miscellaneous HTTP Utilities.

Helpers for dealing with HTTP requests.

Implements HTTP Basic Authentication. This module may add digest authentication in the future.

Convert Haskell values to and from HTTP API data such as URL pieces, headers and query parameters.

Convert Haskell values to and from HTTP API data such as URL pieces, headers and query parameters.

Bindings for The OAuth 2.0 Authorization Framework: Bearer Token Usage RFC6750 https://www.rfc-editor.org/rfc/rfc6750

Abstracting over HTTP libraries

Separate module for HTTP actions, using a proxy server if one exists.

A trivial web server. This web server promotes a Request to IO Response function into a local web server. The user can decide how to interpret the requests, and the library is intended for implementing Ajax APIs. initServerLazy (and assocated refactorings), and Chunking support was written by Henning Thielemann. Handling of POST-based payloads was been written by Brandon Moore. initServerBind support was written by John Van Enk.

HTTP(S)-specific wait functions, for waiting on servers.

This module provides client which can automatically generate querying functions for each endpoint just from the type representing your API.