You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you use a WebSocket Lambda Custom Authorizator and this result is 'allow', all socket messages has the requestContext with the Authorization object. This is actually sent with the $connect route only.
Expected behavior/code
The requestContext need to be present on all routes, like the API Gateway behavior.
Environment
serverless version: [3.14.0]
serverless-offline version: [8.7.0]
node.js version: [e.g. v14.9.0]
OS: [Ubuntu 21.10]
Possible Solution
I will open a pull request with the code fix.
The text was updated successfully, but these errors were encountered:
Bug Report
Current Behavior
When you use a WebSocket Lambda Custom Authorizator and this result is 'allow', all socket messages has the requestContext with the Authorization object. This is actually sent with the $connect route only.
Expected behavior/code
The requestContext need to be present on all routes, like the API Gateway behavior.
Environment
serverless
version: [3.14.0]serverless-offline
version: [8.7.0]node.js
version: [e.g. v14.9.0]OS
: [Ubuntu 21.10]Possible Solution
I will open a pull request with the code fix.
The text was updated successfully, but these errors were encountered: