Annotate
.editorconfig @ 12586:4c8941b5b05e
0.12
core.s2smanager: Don't remove unrelated session on close of bidi session
Normally with bidi, any outgoing connection should be the same as the
incoming, hence when closing a bidi connection it should be removed as a
route to the remote server. However it is not guaranteed, a remote bidi-capable server
might have decided to open a new connection for some reason. This can
lead to a situation where there are two bidi connections, and the s2sout
route is a locally initiated s2sout connection. In this case, such a
s2sout connection should be kept.
Noticed in a rare case where bidi has just been enabled on a running
server, and something establishes new connections immediately when a
connection is closed.
| author |
Kim Alvefur <zash@zash.se> |
| date |
Mon, 27 Jun 2022 01:22:36 +0200 |
| parent |
11706:56feb0cf7052 |
| child |
13191:1266efb7101c |
| rev |
line source |
|
11706
|
1 root = true
|
|
|
2
|
|
|
3 [*]
|
|
|
4 end_of_line = lf
|
|
|
5 indent_style = tab
|
|
|
6 insert_final_newline = true
|
|
|
7 trim_trailing_whitespace = true
|
|
|
8
|
|
|
9 [CHANGES]
|
|
|
10 indent_size = 4
|
|
|
11 indent_style = space
|
|
|
12
|
|
|
13 [configure]
|
|
|
14 indent_size = 3
|
|
|
15 indent_style = space
|
|
|
16
|
|
|
17 [**.xml]
|
|
|
18 indent_size = 2
|
|
|
19 indent_style = space
|
