是什么导致 express.js 请求中的可读字段设置为 false？

Question

New to expressjs and trying to debug the following issue I'm having locally:

1. The GET /health endpoint check works with 200 status response
2. the POST /login endpoint doesn't even appear to fire when running locally (I added a "console.log" statement in the corresponding controller function that would be called by the express.js router and it never gets fired) - what I notice when I do console.log(req) in the main error handler is that this readable field is marked false whereas in the /health endpoint it's marked true:

    req: IncomingMessage {
        _readableState: ReadableState {
          objectMode: false,
          highWaterMark: 16384,
          buffer: BufferList { head: null, tail: null, length: 0 },
          length: 0,
          pipes: null,
          pipesCount: 0,
          flowing: true,
          ended: true,
          endEmitted: true,
          reading: false,
          sync: false,
          needReadable: false,
          emittedReadable: false,
          readableListening: false,
          resumeScheduled: false,
          emitClose: true,
          autoDestroy: false,
          destroyed: false,
          defaultEncoding: 'utf8',
          awaitDrainWriters: null,
          multiAwaitDrain: false,
          readingMore: false,
          decoder: null,
          encoding: null,
          [Symbol(kPaused)]: false
        },
        readable: false,

This just started happening in the past day or so so it's really baffling what change could have been made that would affect the POST /login endpoint's ability to fire when the server is run locally.

Answer 1

An express request is a IncomingMessage which is a readable stream and inherits its .readable property :

Is true if it is safe to call readable.read() , which means the stream has not been destroyed or emitted 'error' or 'end'.

In short it means that the stream has not yet been completely consumed. Since the body of a GET request is ignored (it has none), none of your middlewares will have read it, in contrast to the POST request. So this is expected, and doesn't help with your actual problem.