|
|
|
|
|
|
| Synopsis |
|
|
|
|
| Response object
|
|
|
| Represents an HTTP response
| Instances | |
|
|
|
| The body of the response
|
|
|
| The HTTP headers of the response
|
|
|
| HTTP status code
|
|
|
| Cookies to be set. Uses Cookie from Network.CGI.Cookie
|
|
|
| A string with case insensitive equality and comparisons.
| | Constructors | | Instances | |
|
|
| Cookie |
|
| Building Response objects
|
|
|
Build a Response from a list of Response transformation functions
and an initial Response.
This is a convenient way of creating responses:
resp = buildResponse [ setHeader "Location" foo
, setStatus 302
] utf8HtmlResponse
|
|
|
| Add a string to a response
|
|
|
| Set the HTTP status code of a response
|
|
|
| Set an HTTP header. Previous values (if present) will be overwritten
|
|
|
| Add cookie to a response. Cookie structure is from Network.CGI.Cookie
|
|
|
| Delete the named cookie in the client
|
|
| standardCookie |
|
| expireCookie |
|
| Starting points for Response objects
|
|
|
| An empty text/plain response of a given charset
|
|
|
| An empty UTF8 text/plain response. The user is responsible
for ensuring that that content added to this response is actually
UTF8 ByteStrings.
|
|
|
| An empty text/html response of a given charset
|
|
|
| An empty UTF8 text/html response. The user is responsible
for ensuring that that content added to this response is actually
UTF8 ByteStrings.
|
|
|
| A basic, empty 200 OK response
|
|
|
| Create an HTTP 302 redirect
|
|
| Using Response objects
|
|
|
Convert a Response into the format needed for HTTP.
Copied from Network.CGI.Protocol, thank you Bjorn Bringert :-)
|
|
| Produced by Haddock version 2.4.2 |