Comments (3)
sergey-rud
commented on June 14, 2024
2
I agree. Documentation is seriously flawed. Also I cannot find any documentation about what responses will be returned in different cases:
- Message successfully sent (200)
- Message sent to non-existing connectionId (403)
- Message sent to closed connectionId (410)
- What response would be if we sent message to @connections API and forget to encode @ character (504)
- etc.
from amazon-api-gateway-developer-guide.
dianeo
commented on June 14, 2024
1
I think this link will help: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/apigatewaymanagementapi.html
from amazon-api-gateway-developer-guide.
aleclarson
commented on June 14, 2024
@dianeo How is that link meant to help? Can you point to where it talks about the @connections endpoint?
from amazon-api-gateway-developer-guide.
Related Issues (20)
- Customizing HTTP API access logs there is no mention of cloudwatch log retention HOT 2
- API Gateway Throttling Calculation HOT 1
- the use of region-specific API Gateway account IDs HOT 1
- IAM policy is not able to Deny access to custom WebSocket routes for $connected users HOT 1
- Massage to all clients on websocket HOT 1
- Set up asynchronous invocation of the backend Lambda function Guide is outdated HOT 5
- Lacking documentation on mixed text/binary payloads for http proxy integration HOT 1
- Link to get-client-certificate of AWS CLI is outdated HOT 1
- HTTP API Parameter Mapping doc, wrongfully states body can be transformed HOT 1
- Correct descriptions of WebSocket API CloudWatch metrics HOT 1
- aws api
- Update JSON to YAML for API Gateway resource policy examples HOT 1
- Missing indentation on example
- Documentation Export HOT 1
- Steps are not cleared for API Gateway integration HOT 1
- The token payload is modified before being passed to event.requestContext.authorizer.claims HOT 1
- "API developer" in "AWS Gateway concepts" is confusing HOT 1
- "Callback URL" in "AWS Gateway concepts" wording HOT 1
- Small inaccuracies in "Tutorial: Build an API Gateway REST API with Lambda non-proxy integration" HOT 1
- Possible error in type for requestParams for PostToConnectionCommand HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from amazon-api-gateway-developer-guide.