Changelog for wai-handler-hal-0.4.0.2

Revision history for wai-handler-hal

Union single and multi-value query parameters and headers when converting a hal ProxyRequest to a wai Request

Use a NonEmpty list when consuming the result of getAddrInfo.
When resolving source IPs, do not require AF_INET (IPv4) addresses. This allows IPv6 source addresses to be passed through to the underlying wai Application.

New function: Wai.Handler.Hal.runWithOptions :: Options -> Application -> ProxyRequest NoAuthorizer -> ProxyResponse. This provides a convenient way to pass custom Options without all the bells and whistles of runWithContext.
Instead of guessing whether a given response Content-Type should be sent as text or base64-encoded binary, Options now contains a binaryMediaTypes :: [MediaType], which lists the media types that should be base64-encoded. This should match the binaryMediaTypes setting you have configured on the API Gateway that integrates with your Lambda Function.

See: Content type conversion in API Gateway in the Amazon API Gateway Developer Guide.

Accidental breaking change: more elaborate Content-Type headers like Content-Type: application/json; charset=utf-8 are now encoded as if they were binary payloads. This release has been deprecated.
Breaking change: add Options record parameter to runWithContext, toWaiRequest and fromWaiResponse.
Provide a defaultOptions.
Make whether or not to run base64-encoding on the response body customizable through Options.binaryMimeType.

Breaking change: toWaiRequest now sorts request headers and query string parameters.

When API Gateway sends nonsense IPs during a test invocation, sub in 127.0.0.1 instead of exploding. #3
Removed debug prints left in by mistake.