Get the original Wai Request object

Read a header

Read a header without converting it to text

Read all cookies. The cookie value will already be urldecoded.

Read a cookie. The cookie value will already be urldecoded. Note that it is more efficient to use cookies if you need do access many cookies during a request handler.

Returns the current request method, e.g. GET

Tries to dected the preferred format of the response using the Accept header

Get the raw request body

Parse the request body as json

Parse the request body as json and fails with 400 status code on error

Get uploaded files

Get all request (POST + GET) params

Get all request GET params

Get all request POST params

Read a request param. Spock looks POST variables first and then in GET variables

Like param, but outputs an error when a param is missing

Get the context of the current request

Run an Action in a different context

Set a response status

Set a response header. If the response header is allowed to occur multiple times (as in RFC 2616), it will be appended. Otherwise the previous value is overwritten. See setMultiHeader.

Redirect to a given url

Abort the current action and jump the next one matching the route

Cookie settings

Default cookie settings, equals

CookieSettings
  { cs_EOL      = CookieValidForSession
  , cs_HTTPOnly = False
  , cs_secure   = False
  , cs_domain   = Nothing
  , cs_path     = Just "/"
  }

Setting cookie expiration

Set a cookie. The cookie value will be urlencoded.

Delete a cookie

Send a ByteString as response body. Provide your own "Content-Type"

Send a lazy ByteString as response body. Provide your own "Content-Type"

Set a response header that can occur multiple times. (eg: Cache-Control)

Send text as a response body. Content-Type will be "text/plain"

Send a text as response body. Content-Type will be "text/html"

Send a file as response

Send json as response. Content-Type will be "application/json"

Use a StreamingBody to generate a response.

Use a custom Response generator as response body.

Respond to the request by running an Application. This is usefull in combination with wildcard routes. This can not be used in combination with other request consuming combinators like jsonBody, body, paramsPost, ...

Respond to the request by running a Middleware. This is usefull in combination with wildcard routes. This can not be used in combination with other request consuming combinators like jsonBody, body, paramsPost, ...

If the Spock application is used as a middleware, you can use this to pass request handling to the underlying application. If Spock is not uses as a middleware, or there is no underlying application this will result in 404 error.

Modify the vault (useful for sharing data between middleware and app)

Query the vault

Convenience Basic authentification provide a title for the prompt and a function to validate user and password. Usage example:

get ("auth" <//> var <//> var) $ \user pass ->
      let checker user' pass' =
              unless (user == user' && pass == pass') $
              do setStatus status401
                 text "err"
      in requireBasicAuth "Foo" checker $ \() -> text "ok"

"Lower level" basic authentification handeling. Does not set any headers that will promt browser users, only looks for an Authorization header in the request and breaks it into username and passwort component if present