Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update APIGatewayProxyRequest for the new WebSocket Fields #367

Closed
normj opened this issue Dec 19, 2018 · 2 comments
Closed

Update APIGatewayProxyRequest for the new WebSocket Fields #367

normj opened this issue Dec 19, 2018 · 2 comments
Labels
feature-request A feature should be added or improved.

Comments

@normj
Copy link
Member

normj commented Dec 19, 2018

The APIGatewayProxyRequest event class needs to be updated to support the new properties for WebSockets like DomainName and ConnectionId.

@normj
Copy link
Member Author

normj commented Feb 1, 2019

Feature merged into dev branch to go out next release.

@normj normj closed this as completed Feb 1, 2019
@diegosasw
Copy link

diegosasw commented Feb 22, 2021

@normj do you have any example on how a json event from API Gateway websocket looks like?

I'm wondering whether I should be able to use CURL to post some json to my lambda running on a local AWS Runtime Interface Emulator pretending that it's coming from a websocket, since SAM does not support websockets and I can't test that integration locally.

Is this a good example and the only difference from a REST api event is that it includes connection id and domain?
https://github.com/FranciscoJCLus/aws-lambda-dotnet/blob/61e096a38ca67947bdc220d1dddfd142a3764f47/Libraries/test/EventsTests/proxy-event.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

2 participants