Releases: logandk/serverless-wsgi
Release 1.7.8
Release 1.7.7
Release 1.7.6
Release 1.7.5
1.7.5
Bugs
-
Fix integration with virtualenv for latest version (20.x)
-
Fix wrong encoding of error messages during packaging (#122, #139)
Jan Varho
Release 1.7.4
1.7.4
Bugs
- Return error exit code when
exec
,command
,manage
orflask
commands fail (#114) - Display output from failing
command
invocations instead of throwing exception (#107)
Release 1.7.3
1.7.3
Features
-
Add
--ssl
flag tosls wsgi serve
(#103) -
Add log message when skipping handler on warmup events (#95)
-
Add options for disabling threading and setting number of processes when invoking
sls wsgi serve
(#100)Bryan Worrell
-
Allow use of CloudFront with a pre-set path (#101)
Paul Bowsher
Bugs
-
Properly decode event
path
into environPATH_INFO
(#93) -
Fix local serving when package
individually: true
and functionmodule
are provided (#98) -
Fix Flask CLI invocation of built-in commands (#99)
Mischa Spiegelmock
Release 1.7.2
1.7.2
Features
-
Support multi-value query string parameters (#87)
Jan Varho
-
Support multi-value headers in request and response
-
Add
sls wsgi flask
andsls wsgi flask local
commands (#86)
Release 1.7.1
1.7.1
Features
- Add local versions of manage, command and exec commands (#79)
- Support serverless-python-requirements packaging with
individually
andmodule
configuration (#85)
Release 1.7.0
1.7.0
Features
- Rename
.wsgi_app
to.serverless-wsgi
(to follow convention fromserverless-rack
) - Check for werkzeug presence in bundle or issue warning (#80)
Bugs
- The
wsgi.handler
has been renamed towsgi_handler.handler
due to a naming
conflict with an internal AWS wsgi module. A warning and workaround is issued in order
to prevent breaking existing configuration files (#84)
Release 1.6.1
1.6.1
Features
- Use proper namespacing for custom WSGI environment variables:
serverless.authorizer
,serverless.event
andserverless.context
.
Note:API_GATEWAY_AUTHORIZER
,event
andcontext
will be deprecated later. - Permute header casings for multiple values of any header, not just
Set-Cookie