Unhandled exception when receiving websocket error

Open

#170 opened on Mar 7, 2019 7 comments 0 reactions 1 assignee View on GitHub

@compulim is already working on this.

Since Aug 11, 2020.

Assessment

This issue has not been assessed yet.

Description

Bot Services customer-replied-to customer-reported

It happens occasionally when the websocket connection returns 400.

Can be easily reproduced by providing a non-working domain:

    var directLine = new DirectLine({
      secret: <bot-secret>,
      domain: 'https://europe.directline.botframework.com/v3/directline'
    });

Trace:

Error: Unexpected server response: 400                                                           
    at ClientRequest.req.on (E:\Project\node_modules\ws\lib\websocket.js:559:5)                                                                                                       
    at ClientRequest.emit (events.js:159:13)                                                     
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:550:21)                
    at HTTPParser.parserOnHeadersComplete (_http_common.js:115:23)                               
    at TLSSocket.socketOnData (_http_client.js:439:20)                                           
    at TLSSocket.emit (events.js:159:13)                                                         
    at addChunk (_stream_readable.js:265:12)                                                     
    at readableAddChunk (_stream_readable.js:252:11)                                             
    at TLSSocket.Readable.push (_stream_readable.js:209:10)                                      
    at TLSWrap.onread (net.js:608:20)

Dominant language: TypeScript
Stars: 199
Forks: 133
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

docs: manual client injection examples reference removed exports Open

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

vitejs/devtools#589 · 1 comment · Opened Sep 25, 2026
🔒 [IBM OSPO Security Notification] — IBM/node-sdk-core Open

security

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

IBM/node-sdk-core#373 · Opened Sep 25, 2026
[fullsend] E2E: topology — Tekton pipeline status decorator timeout on Topology tab Open

e2e-failure ready-to-code

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

redhat-developer/rhdh-plugin-export-overlays#3937 · Opened Sep 25, 2026
The open-first recovery advice falls back to --base main, contradicting the fetched base Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

victorstein/herdr-plugin-pipeline#121 · Opened Sep 25, 2026
Finish the #680 label rename: audit-report 'Layout flags' heading and CLAUDE.md Open

chore

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

offlinecv/OfflineCV#1018 · Opened Sep 25, 2026

More TypeScript issues