Description of changes:
API Gateway Websocket APIs currently error out when using this library to handle requests since the RequestContext.Http object is null. This change allows this library to be used with Websocket APIs by setting the Http.Path to the RouteKey and the Http.Method fixed as POST. This approach requires the user to reference the same lambda for the RouteKeys which they want handled by the lambda server.
The changes to the APIGatewayHttpApiV2ProxyFunction class is minimal and adds a APIGatewayWebsocketApiV2ProxyFunction class and corresponding changes to the Amazon.Lambda.AspNetCoreServer.Hosting project to provide for a Websocket option.
All tests that were passing in the current master branch are passing in the PR.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue #, if available:
Description of changes: API Gateway Websocket APIs currently error out when using this library to handle requests since the
RequestContext.Http
object is null. This change allows this library to be used with Websocket APIs by setting theHttp.Path
to theRouteKey
and theHttp.Method
fixed asPOST
. This approach requires the user to reference the same lambda for theRouteKey
s which they want handled by the lambda server.The changes to the
APIGatewayHttpApiV2ProxyFunction
class is minimal and adds aAPIGatewayWebsocketApiV2ProxyFunction
class and corresponding changes to theAmazon.Lambda.AspNetCoreServer.Hosting
project to provide for a Websocket option.All tests that were passing in the current master branch are passing in the PR.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.