- Update Python support to 3.5-3.7, as 3.4 has reached its end of life.
- If API Gateway event includes
requestContext
, for example for custom authorizers, pass it in the WSGIenviron
asapig_wsgi.request_context
.
- Revert adding
statusDescription
because it turns out API Gateway doesn't ignore it but instead fails the response with an internal server error.
- Change
statusCode
returned to API Gateway / ALB to an integer. It seems API Gateway always supported both strings and integers, whilst ALB only supports integers. - Add
statusDescription
in return value. API Gateway doesn't seem to use this whilst the ALB documentation mentions it as supported.
- Drop Python 2 support, only Python 3.4+ is supported now.
- Temporarily restore Python 2 support. This is in order to fix a packaging
metadata issue that 2.0.0 was marked as supporting Python 2, so a new release
is needed with a higher version number for
pip install apig-wsgi
to resolve properly on Python 2. Version 2.0.2+ ofapig-wsgi
will not support Python 2.
- Drop Python 2 support, only Python 3.4+ is supported now.
- If
exc_info
is passed in, re-raise the exception (previously it would be ignored and crash in a different way). This isn't the nicest experience, however the behaviour is copied fromwsgiref
's simple server, and most WSGI applications implement their own exception conversion to a "500 Internal Server Error" page already. - Noted that the EC2 ALB to Lambda integration is also supported as it uses the same event format as API Gateway.
- Work with base64 encoded
body
values in requests from API Gateway.
- Fix crash using binary support for responses missing a
Content-Type
header.
- Remove debug
print()
- Add
binary_support
flag to enable sending binary responses, if enabled on API Gateway.
- First release on PyPI, working basic integration for WSGI apps on API Gateway.