为什么onmail侦听器不处理初始SSE事件？

Question

在本例中，客户端通过创建新的EventSource连接到Node Express服务器。服务器在初始连接时发送SSE事件，然后每隔30秒发送一次。问题是客户端的onmessage处理程序不是由连接时发送的初始SSE事件触发的，而是由所有后续事件触发的。如果我在建立连接后立即停止服务器，这实际上会在客户端中触发一个事件，表明数据实际上是在片刻之前没有处理的情况下收到的（或者初始res.write仅在服务器关闭时触发）：

服务器：

let data = {mydata: 123};

function eventsHandler(req, res, next) {

  const headers = {
    "Content-Type": "text/event-stream",
    Connection: "keep-alive",
    "Cache-Control": "no-cache",
  };

  res.writeHead(200, headers);
  // After client opens connection we send data string, but client doesn't handle this correctly
  // Event is only triggered on client if I stop the server after sending this message
  res.write(`data: ${JSON.stringify(data)}\n\n`);
  console.log("sent SSE");

  const clientId = Date.now();
  console.log(clientId, " connected");
  const newClient = {
    id: clientId,
    res,
  };
  clients.push(newClient);

  req.on("close", () => {
    console.log(`${clientId} Connection closed`);
    clients = clients.filter((c) => c.id !== clientId);
  });
}

// these events are received and handled correctly on client
function sendEventsToAll(datadict) {
  clients.forEach((c) => c.res.write(`data: ${JSON.stringify(datadict)}\n\n`));
}

// Route to open SSE connection
app.get("/events", eventsHandler);

// Loop to send SSE every 30 seconds - these are all received and handled correctly
async function wait() {
  sendEventsToAll(data);
  setTimeout(wait, 30000);
}

wait();

浏览器：

      const events = new EventSource(url)

      // This handles every SSE event except the one that is written immediately upon connection
      // If I stop the server after connection, this will trigger and reveal the data was received but not handled
      events.onmessage = event => {
        const newData = JSON.parse(event.data)
        console.log("newData", newData)
      }

编辑：我还应该补充一点，我正在使用nginx作为反向代理-这会不会因为某种原因而缓冲第一个res.write而不是立即发送它？

Answer 1

这是由nginx中的proxy\u缓冲造成的，该缓冲默认为“开”。

在nginx配置中关闭此选项解决了问题：

server {
# server config here...

   location / {
   # proxy config here...
   proxy_buffering off; # resolves issue
   }

}