Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

client reset observe failed

See original GitHub issue

Issue Description

in client side, i want to send RST packet to server.

req.on('response', function(res) {
  console.log("---------------------response---------------------");
  console.log(res.headers);

  var rcvCount = 5;
  res.on('data', function(data) {
    console.log(data);
    rcvCount--
    if(rcvCount == 0){
      //it will throw new Error: Empty messages must be empty
      req.reset();
    }
  });
})
req.end()

when i call req.reset(), it will throw Empty messages must be empty error

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:8

Top GitHub Comments

1reaction

Pluuutocommented, Nov 8, 2017

I have almost the same problem. When I am using “res.reset()” at server-end.

const coap = require('coap')

const server = coap.createServer()

server.on('request', (req, res) => {
  console.log(`Receive request: ${req.url}`)
  res.reset()
})

server.listen(5683, '127.0.0.1')

It will cause client-end throwing “Empty messages must be empty error”. Using wireshark to capture and I find server-end sending NON msg with ‘5.00 Internal Server Error’ and body ‘Empty messages must be empty’ after send RST msg.

NON msg has the same token with the NON request which client-end sent. I think this cause client-end throws error. I don’t know why coap source code deal with reset on this way, maybe it’s a bug? (reference to ‘fastseries’ lib)

0reactions

JKRhbcommented, Jun 16, 2021

@robertbbb @lucarv Could you give a bit more context under which conditions the error occured? (Sorry for the late follow-up question.)