Wai -package:katip-wai

This module defines a generic web application interface. It is a common protocol between web servers and web applications. The overriding design principles here are performance and generality. To address performance, this library uses a streaming interface for request and response bodies, paired with bytestring's Builder type. The advantages of a streaming API over lazy IO have been debated elsewhere and so will not be addressed here. However, helper functions like responseLBS allow you to continue using lazy IO if you so desire. Generality is achieved by removing many variables commonly found in similar projects that are not universal to all servers. The goal is that the Request object contains only data which is meaningful in all circumstances. Please remember when using this package that, while your application may compile without a hitch against many different servers, there are other considerations to be taken when moving to a new backend. For example, if you transfer from a CGI application to a FastCGI one, you might suddenly find you have a memory leak. Conversely, a FastCGI application would be well served to preload all templates from disk when first starting; this would kill the performance of a CGI application. This package purposely provides very little functionality. You can find various middlewares, backends and utilities on Hackage. Some of the most commonly used include:

• warp http://hackage.haskell.org/package/warp
• wai-extra http://hackage.haskell.org/package/wai-extra

Have a look at the README for an example of how to use this library.

Test a Application Example usage:

exampleApplication :: Wai.Application
exampleApplication req sendResp = do
lb <- strictRequestBody req
sendResp $ responseLBS HTTP.ok200 (requestHeaders req) lb

spec :: Spec
spec =
waiClientSpec exampleApplication $
describe "get" $
it "can GET the root and get a 200" $ do
resp <- get "/"
liftIO $ responseStatus resp `shouldBe` ok200

Types and functions for testing wai endpoints using the tasty testing framework.

A light-weight wrapper around Network.Wai to provide easy pipes support.

This module provides remote monitoring of a running process over HTTP. It can be used to run an HTTP server that provides both a web-based user interface and a machine-readable API (e.g. JSON.) The former can be used by a human to get an overview of what the program is doing and the latter can be used by automated monitoring tools. Typical usage is to start the monitoring server at program startup

main = do
forkServer "localhost" 8000
...

and then periodically check the stats using a web browser or a command line tool (e.g. curl)

$ curl -H "Accept: application/json" http://localhost:8000/

wai-session server-side session support. Please note that this frontend has some limitations:

• Cookies use the Max-age field instead of Expires. The Max-age field is not supported by all browsers: some browsers will treat them as non-persistent cookies.
• Also, the Max-age is fixed and does not take a given session into consideration.

Module for using a WAI Middleware as an X-Ray client

Web Application Interface. Provides a common protocol for communication between web applications and web servers. API docs and the README are available at http://www.stackage.org/package/wai.

Wrap up a normal WAI application as a Yesod subsite. Ignore parent site's middleware and isAuthorized.

Like WaiSubsite, but applies parent site's middleware and isAuthorized.