Hoogle Search

Within LTS Haskell 24.67 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. requestFromURI :: MonadThrow m => URI -> m Request

    http-conduit Network.HTTP.Client.Conduit

    Convert a URI into a Request. This can fail if the given URI is not absolute, or if the URI scheme is not "http" or "https". In these cases the function will throw an error via MonadThrow. This function defaults some of the values in Request, such as setting method to GET and requestHeaders to []. A Request created by this function won't cause exceptions on non-2XX response status codes.

  2. requestFromURI_ :: URI -> Request

    http-conduit Network.HTTP.Client.Conduit

    Same as requestFromURI, but if the conversion would fail, throws an impure exception.

  3. setRequestCheckStatus :: Request -> Request

    http-conduit Network.HTTP.Client.Conduit

    Modify the request so that non-2XX status codes generate a runtime StatusCodeException, by using throwErrorStatusCodes

  4. setRequestIgnoreStatus :: Request -> Request

    http-conduit Network.HTTP.Client.Conduit

    Modify the request so that non-2XX status codes do not generate a runtime StatusCodeException.

  5. HttpExceptionRequest :: Request -> HttpExceptionContent -> HttpException

    http-conduit Network.HTTP.Conduit

    Most exceptions are specific to a Request. Inspect the HttpExceptionContent value for details on what occurred.

  6. InvalidRequestHeader :: ByteString -> HttpExceptionContent

    http-conduit Network.HTTP.Conduit

    The given request header is not compliant (e.g. has newlines)

  7. data Request

    http-conduit Network.HTTP.Conduit

    All information on how to connect to a host and what should be sent in the HTTP request. If you simply wish to download from a URL, see parseRequest. The constructor for this data type is not exposed. Instead, you should use either the defaultRequest value, or parseRequest to construct from a URL, and then use the records below to make modifications. This approach allows http-client to add configuration options without breaking backwards compatibility. For example, to construct a POST request, you could do something like:

    initReq <- parseRequest "http://www.example.com/path"
    let req = initReq
    { method = "POST"
    }
    
    For more information, please see http://www.yesodweb.com/book/settings-types. Since 0.1.0

  8. data RequestBody

    http-conduit Network.HTTP.Conduit

    When using one of the RequestBodyStream / RequestBodyStreamChunked constructors, you must ensure that the GivesPopper can be called multiple times. Usually this is not a problem. The RequestBodyStreamChunked will send a chunked request body. Note that not all servers support this. Only use RequestBodyStreamChunked if you know the server you're sending to supports chunked request bodies. Since 0.1.0

  9. RequestBodyBS :: ByteString -> RequestBody

    http-conduit Network.HTTP.Conduit

    No documentation available.

  10. RequestBodyBuilder :: Int64 -> Builder -> RequestBody

    http-conduit Network.HTTP.Conduit

    No documentation available.

Page 175 of many | Previous | Next