blocks|key|2978708|text|我猜你只是关闭了连接(杀死它)。我还没有看到任何关于优雅断开的讨论。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2978709|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I guess you just close the connection (kill it). I have not seen any talk about graceful disconnect.

blocks|key|3264369|text|node.js：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3264370|http.createServer(function+(req,+res)+{

++++//...

++++//+client+closes+connection
++++res.socket.on('close',+function+()+{
++++++res.end();
++++++//...
++++});

});|code-block|syntax|javascript|3264371|单点登录服务器在node.js中的实现参见示例：|3264372|https://github.com/Yaffle/EventSource/blob/master/nodechat/server.js|offset|length|3264373|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|1W|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|W|8|@]|9|@$K|X|L|Y|1|Z]]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|J]]]]

node.js:

<pre><code>http.createServer(function (req, res) {

 //...

 // client closes connection
 res.socket.on('close', function () {
 res.end();
 //...
 });

});
</code></pre>

see example for implementation of SSE server in node.js:

<a href="https://github.com/Yaffle/EventSource/blob/master/nodechat/server.js" rel="nofollow">https://github.com/Yaffle/EventSource/blob/master/nodechat/server.js</a>

blocks|key|2978759|text|您可以更改服务器发送的内容类型，而不是"text/event-stream“。这将关闭客户端事件源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2978760|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

you can change the content-type the server sents other than "text/event-stream". 
This will close the clients eventsource.

blocks|key|3264437|text|警告：如果在node.js中使用程序包管理服务器发送的事件，直接调用response.end()可能会导致程序包在关闭后发送额外数据，这将使服务器崩溃，并显示“关闭后写入”错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|3264438|我的变通方法是调用response.emit('close')，而不是直接调用response.end()，它允许包处理关闭。|3264439|http.ServerResponse+>+Event.close上的Node.js文档|3264440|https://nodejs.org/api/http.html#http_event_close_1|3264441|entityMap|0|LINK|mutability|MUTABLE|url^0|0|2|Y|E|0|9|M|13|E|0|0|X|0|0|1F|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|Y|8|@$9|Z|A|10|B|D]|$9|11|A|12|B|D]]|E|@]|F|$]]|$1|I|3|J|5|6|7|13|8|@$9|14|A|15|B|C]]|E|@]|F|$]]|$1|K|3|L|5|6|7|16|8|@]|E|@$9|17|A|18|1|19]]|F|$]]|$1|M|3|-4|5|6|7|1A|8|@]|E|@]|F|$]]]|N|$O|$5|P|Q|R|F|$S|L]]]]

Caution: If you use a package to manage server-sent events in node.js, making a direct call to <code>response.end()</code> may cause the package to send additional data after <code>response.end()</code>, and this will crash the server with a "WRITE after close" error.

Instead of directly calling <code>response.end()</code>, my workaround was to call <code>response.emit('close')</code>, which allowed the package to handle the close.

Node.js documentation on http.ServerResponse > Event.close:

<a href="https://nodejs.org/api/http.html#http_event_close_1" rel="nofollow noreferrer">https://nodejs.org/api/http.html#http_event_close_1</a>

blocks|key|1363809|text|如果要从客户端关闭连接，则不能使用res.end()，而且稍后可能会导致ERR_STREAM_WRITE_AFTER_END错误。如果是这样的话，你最好撤销你在路由中添加的逻辑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1363810|可以在Node.JS+Server+Sent+Events:+Route+continues+to+run+after+res.end()+resulting+in+ERR_STREAM_WRITE_AFTER_END+error中找到一个例子。|offset|length|1363811|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/59797523/node-js-server-sent-events-route-continues-to-run-after-res-end-resulting-in?noredirect=1#comment105798817_59797523[here][1]^0|0|3|34|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

res.end() is not the way to go if the connection is being closed from the client side and might result in a ERR_STREAM_WRITE_AFTER_END error later. If this the case, you are better off just undoing the logic that you added in the route. 

An example can be found <a href="https://stackoverflow.com/questions/59797523/node-js-server-sent-events-route-continues-to-run-after-res-end-resulting-in?noredirect=1#comment105798817_59797523[here][1]">Node.JS Server Sent Events: Route continues to run after res.end() resulting in ERR_STREAM_WRITE_AFTER_END error</a>.

blocks|key|5049960|text|因此，我到处寻找内置到协议中的解决方案，但似乎没有。如果您的服务器调用response.emit('close')或response.end()，客户端将把它当作错误处理，并尝试重新连接到服务器。(至少在Chrome的情况下，它将尝试无限期地重新连接，除非它认为网络错误是致命的)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5049961|因此，无论以何种方式，您的客户端都必须关闭连接。这就只剩下两个选择了。第一，简单地假设来自服务器的任何错误都应该关闭EventSource。|5049962|const+sse+=+new+EventSource('/events')
sse.onmessage+=+m+=>+console.log(m.data)
sse.onerror+=+()+=>+sse.close()|code-block|syntax|javascript|5049963|不过，上面的内容还有一些需要改进的地方。我们假设网络错误是正常关机，但事实可能并非如此。也可能在某些情况下，我们确实需要重新连接行为。|5049964|所以，为什么我们不直接要求客户端优雅地关闭自己呢！我们有一种从服务器向客户端发送消息的方法，所以我们需要做的就是从服务器发送一条消息，上面写着“关闭我”。|5049965|//+client.js
const+maxReconnectTries+=+3

let+reconnectAttempts+=+0
const+sse+=+new+EventSource('/events')
sse.onmessage+=+m+=>+{
++const+{+type,+data+}+=+JSON.parse(m.data)
++if+(type+===+'close')+sse.close()
++else+console.log(data)
}
sse.onerror+=+()+=>+{
++if+(reconnectAttempts+>+maxReconnectTries)+{
++++sse.close()
++++alert("We+have+a+baaad+network+error!")
++}+else+{
++++reconnectAttempts%2B%2B
++}
}|5049966|//+server.js
const+express+=+require('express')


function+sendEvent(res,+type,+data)+{
++res.write(`data:+${JSON.stringify({+type,+data+})}\n\n`)
}

function+sseHandler(req,+res)+{
++response.writeHead(200,+{
++++'Connection':+'keep-alive',
++++'Content-Type':+'text/event-stream',
++++'Cache-Control':+'no-cache'
++}

++let+manualShutdown
++request.on('close',+()+=>+{
++++console.log('disconnected.')
++++clearTimeout(manualShutdown)++//+prevent+shutting+down+the+connection+twice
++})
++
++sendEvent(res,+'message',+`Ping+sent+at+${new+Date()}`)

++//+when+it+comes+time+to+shutdown+the+event+stream+(for+one+reason+or+another)
++setTimeout(()+=>+{
++++sendEvent(res,+'close',+null)
++++//+give+it+a+safe+buffer+of+time+before+we+shut+it+down+manually
++++manualShutdown+=+setTimeout(()+=>+res.end(),+clientShutdownTimeout)
++},+10000)
}

const+clientShutdownTimeout+=+2000
const+app+=+express()
app.get('/events',+sseHandler)
app.listen(4000,+()+=>+console.log('server+started+on+4000'))|5049967|这涵盖了安全的客户端/服务器实现所需的所有领域。如果服务器出现问题，我们会尝试重新连接，但仍然可以在出现故障时通知客户端。当服务器想要关闭连接时，它会要求客户端关闭连接。两秒钟后，如果客户端没有关闭连接，我们可以假定出现了错误，并关闭连接服务器端。|5049968|我们在这里做的是在服务器发送事件的基础上构建一个协议。它有一个非常简单的接口：{+"type":+"close"+}告诉客户端关闭服务器，{+"type":+"message",+"data":+{"some":+"data"+}告诉客户端这是一条常规消息。|5049969|entityMap^0|Z|M|1M|E|0|0|0|0|0|0|0|0|13|J|1X|1A|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|18|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|19|8|@]|D|@]|E|$K|L]]|$1|S|3|T|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|1B|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|Z|$]]

So, I've searched around for a solution built into the protocol, and it there does not appear to be one. If your server calls <code>response.emit('close')</code> or <code>response.end()</code>, the client will treat this like an error and attempt to reconnect to the server. (At least in the case of Chrome, it will attempt to reconnect indefinitely, unless it considers the network error fatal).
So it appears that one way or another, your client has to close the connection. That leaves two options. The first, is to simply assume any error from the server should close the EventSource.
<pre class="lang-js prettyprint-override"><code>const sse = new EventSource('/events')
sse.onmessage = m =&gt; console.log(m.data)
sse.onerror = () =&gt; sse.close()
</code></pre>
The above leaves a few things to be desired though. We are assuming that a network error is a graceful shutdown, this may not be the case. There may also be some scenarios where we do want the reconnect behavior.
So instead, why don't we just ask the client to gracefully shutdown itself! We have a way to send messages to the client from the server, so all we need to do is send a message from the server that says &quot;shut me down&quot;.
<pre class="lang-js prettyprint-override"><code>// client.js
const maxReconnectTries = 3

let reconnectAttempts = 0
const sse = new EventSource('/events')
sse.onmessage = m =&gt; {
 const { type, data } = JSON.parse(m.data)
 if (type === 'close') sse.close()
 else console.log(data)
}
sse.onerror = () =&gt; {
 if (reconnectAttempts &gt; maxReconnectTries) {
 sse.close()
 alert(&quot;We have a baaad network error!&quot;)
 } else {
 reconnectAttempts++
 }
}
</code></pre>
<pre class="lang-js prettyprint-override"><code>// server.js
const express = require('express')


function sendEvent(res, type, data) {
 res.write(`data: ${JSON.stringify({ type, data })}\n\n`)
}

function sseHandler(req, res) {
 response.writeHead(200, {
 'Connection': 'keep-alive',
 'Content-Type': 'text/event-stream',
 'Cache-Control': 'no-cache'
 }

 let manualShutdown
 request.on('close', () =&gt; {
 console.log('disconnected.')
 clearTimeout(manualShutdown) // prevent shutting down the connection twice
 })
 
 sendEvent(res, 'message', `Ping sent at ${new Date()}`)

 // when it comes time to shutdown the event stream (for one reason or another)
 setTimeout(() =&gt; {
 sendEvent(res, 'close', null)
 // give it a safe buffer of time before we shut it down manually
 manualShutdown = setTimeout(() =&gt; res.end(), clientShutdownTimeout)
 }, 10000)
}

const clientShutdownTimeout = 2000
const app = express()
app.get('/events', sseHandler)
app.listen(4000, () =&gt; console.log('server started on 4000'))
</code></pre>
This covers all the areas that we need for a safe client/server implementation. If there's an issue on the server, we attempt to reconnect but can still notify the client if there's a failure. When the server wants the connection closed, it asks the client to close the connection. After two seconds, if the client has not shut down the connection we can assume something went wrong and close the connection server side.
What we are doing here is building a protocol on top of server sent events. It has a very simple api: <code>{ &quot;type&quot;: &quot;close&quot; }</code> tells the client to close the server, and <code>{ &quot;type&quot;: &quot;message&quot;, &quot;data&quot;: {&quot;some&quot;: &quot;data&quot; }</code> tells the client this is a regular message.

Regarding this specification: <a href="http://www.w3.org/TR/eventsource/" rel="noreferrer">http://www.w3.org/TR/eventsource/</a>

How does one close the opened connection on the server? Client-side wise it is easy, just call <code>close()</code>, but what should I do on the server? Just kill it?

How to close a "Server-Sent Events"-connection on the server?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

关于此规范：如何关闭服务器上打开的连接？在客户端，这很简单，只需调用close()，但是我应该在服务器端做什么呢？杀了就好?

问如何关闭服务器上的“服务器发送的事件”-connection？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何关闭服务器上的“服务器发送的事件”-connection？EN