Documentation

Does this request appear to have been made over an SSL connection?

This function first checks isSecure, but also checks for headers that may indicate a secure connection even in the presence of reverse proxies.

Note: these headers can be easily spoofed, so decisions which require a true SSL connection (i.e. sending sensitive information) should only use isSecure. This is not always the case though: for example, deciding to force a non-SSL request to SSL by redirect. One can safely choose not to redirect when the request appears secure, even if it's actually not.

Since: 3.0.7

Guess the "application root" based on the given request.

The application root is the basis for forming URLs pointing at the current application. For more information and relevant caveats, please see Network.Wai.Middleware.Approot.

Since: 3.0.7

see requestSizeCheck

Since: 3.0.15

Check request body size to avoid server crash when request is too large.

This function first checks requestBodyLength, if content-length is known but larger than limit, or it's unknown but we have received too many chunks, a RequestSizeException are thrown when user use requestBody to extract request body inside IO.

Since: 3.0.15