Hoogle Search

Within LTS Haskell 24.58 (ghc-9.10.3)

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

Exact lookup

1. TooManyHeaderFields :: HttpExceptionContent

   http-conduit	Network.HTTP.Client.Conduit

   Too many HTTP header fields were returned by the server.

2. managerSetMaxHeaderLength :: Int -> ManagerSettings -> ManagerSettings

   http-conduit	Network.HTTP.Client.Conduit

   No documentation available.

3. managerSetMaxNumberHeaders :: Int -> ManagerSettings -> ManagerSettings

   http-conduit	Network.HTTP.Client.Conduit

   No documentation available.

4. IncompleteHeaders :: HttpExceptionContent

   http-conduit	Network.HTTP.Conduit

   An incomplete set of response headers were returned.

5. InvalidChunkHeaders :: HttpExceptionContent

   http-conduit	Network.HTTP.Conduit

   A chunked response body had invalid headers.

6. InvalidHeader :: ByteString -> HttpExceptionContent

   http-conduit	Network.HTTP.Conduit

   The given response header line could not be parsed

7. InvalidRequestHeader :: ByteString -> HttpExceptionContent

   http-conduit	Network.HTTP.Conduit

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

8. OverlongHeaders :: HttpExceptionContent

   http-conduit	Network.HTTP.Conduit

   Too many total bytes in the HTTP header were returned by the server.

9. TooManyHeaderFields :: HttpExceptionContent

   http-conduit	Network.HTTP.Conduit

   Too many HTTP header fields were returned by the server.

10. requestHeaders :: Request -> RequestHeaders

    http-conduit	Network.HTTP.Conduit

    Custom HTTP request headers The Content-Length and Transfer-Encoding headers are set automatically by this module, and shall not be added to requestHeaders. If not provided by the user, Host will automatically be set based on the host and port fields. Moreover, the Accept-Encoding header is set implicitly to gzip for convenience by default. This behaviour can be overridden if needed, by setting the header explicitly to a different value. In order to omit the Accept-Header altogether, set it to the empty string "". If you need an empty Accept-Header (i.e. requesting the identity encoding), set it to a non-empty white-space string, e.g. " ". See RFC 2616 section 14.3 for details about the semantics of the Accept-Header field. If you request a content-encoding not supported by this module, you will have to decode it yourself (see also the decompress field). Note: Multiple header fields with the same field-name will result in multiple header fields being sent and therefore it's the responsibility of the client code to ensure that the rules from RFC 2616 section 4.2 are honoured. Since 0.1.0

Page 142 of many | Previous | Next