Passing connection option to event handler
- Dominant language
- TypeScript
- Stars
- 147
- Forks
- 96
- Avg merge
- 19h 28m
- Merged PRs (30d)
- 87
Description
### Describe the bug
Not sure if this is a bug or not, but after 5 days, 10 hours a day i feel compelled to post this. The connect function to send to event handler does not seem to work at all with any examples. I constantly get a "Request server is denied as target server is invalid."
I've gone through the entire server sdk and I cant see where the handshake is failing.
In additional it never seems to pass CORS. Copy and pasting example does not work. Implementing CORS properly doesnt work.
### To Reproduce
Copy and past chat code, dev code, all samples of handling connect option into a new pub sub.
We will close this issue if:
- the repro project you share with us is complex. We can't investigate custom projects, so don't point us to such, please.
- if we will not be able to repro the behavior you're reporting
--> https://github.com/Azure/azure-webpubsub/blob/main/samples/javascript/chatapp/sdk/server.js
### Exceptions (if any)
### Further technical details
-javascript, repo is above
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with samples/javascript/chatapp/sdk/server.js and run the smallest chat or pub/sub reproduction using the connect option. Trace the handshake response and CORS behavior, recording the exact target-server error; done means the sample reproduces a specific cause and either works correctly or provides a confirmed minimal failure case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- api, backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100