`SendToConnection()`. When `connectionId` is `""`, return `404 not found`. When `connectionId` is a non-existed connection Id, nothing happens.
- Dominant language
- TypeScript
- Stars
- 147
- Forks
- 96
- Avg merge
- 19h 28m
- Merged PRs (30d)
- 87
Description
https://github.com/Azure/azure-webpubsub/issues/33
`SendToUser` is also the same behavior with empty UserId.
The SDK sends out the request using `https://demo-2.webpubsubdev.azure.com/api/hubs/chat/connections//:send?api-version=2020-10-01` as a result 404 returns.
SDK should validate the parameters first when the parameters are in the path.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the SDK entry points for SendToConnection and SendToUser, focusing on how connectionId and UserId are inserted into the request path. Reproduce the empty-parameter requests described in the issue and confirm that validation prevents the malformed paths and returns the intended not-found behavior; also check the behavior for a non-existent connection ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100