Host/port combination to which we want to proxy.

Set up a reverse proxy server, which will have a minimal overhead.

This function uses raw sockets, parsing as little of the request as possible. The workflow is:

1. Parse the first request headers.
2. Ask the supplied function to specify how to reverse proxy.
3. Open up a connection to the given host/port.
4. Pass all bytes across the wire unchanged.

If you need more control, such as modifying the request or response, use waiProxyTo.

Creates a WAI Application which will handle reverse proxies.

Connections to the proxied server will be provided via http-conduit. As such, all requests and responses will be fully processed in your reverse proxy. This allows you much more control over the data sent over the wire, but also incurs overhead. For a lower-overhead approach, consider rawProxyTo.

Most likely, the given application should be run with Warp, though in theory other WAI handlers will work as well.

Note: This function will use chunked request bodies for communicating with the proxied server. Not all servers necessarily support chunked request bodies, so please confirm that yours does (Warp, Snap, and Happstack, for example, do).

Sends a simple 502 bad gateway error message with the contents of the exception.

The default value for this type.

Convert a WAI application into a raw application, using Warp.