From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62990@debbugs.gnu.org, mail@vasilij.de
Subject: bug#62990: 30.0.50; UDP server closes connection upon receiving an empty packet
Date: Wed, 26 Apr 2023 16:27:48 +0200 [thread overview]
Message-ID: <87bkjasopn.fsf@gmail.com> (raw)
In-Reply-To: <83jzxyu90c.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Apr 2023 15:24:03 +0300")
>>>>> On Wed, 26 Apr 2023 15:24:03 +0300, Eli Zaretskii <eliz@gnu.org> said:
>>
>> I guess we could, but if the application asks us to send an empty
>> packet we should do it.
Eli> I didn't say that the default behavior should be that, I just asked
Eli> whether it is conceivable that someone, somewhere could actually rely
Eli> on the semi-buggy behavior, whereby empty packets aren't sent?
I canʼt conceive of it. If it ever does happen the fix is easy: check
the length of the message before sending it.
>>
>> ie the UDP process is still running and can still receive messages
Eli> And no one could ever expect that? IOW, is this behavior obviously
Eli> wrong?
Yes. The other end has sent a valid UDP packet, and we react by
closing the connection.
Robert
--
next prev parent reply other threads:[~2023-04-26 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 10:36 bug#62990: 30.0.50; UDP server closes connection upon receiving an empty packet Vasilij Schneidermann
2023-04-24 8:51 ` Robert Pluim
2023-04-24 21:04 ` Vasilij Schneidermann
2023-04-25 8:07 ` Robert Pluim
2023-04-26 9:14 ` Robert Pluim
2023-04-26 10:30 ` Eli Zaretskii
2023-04-26 10:35 ` Robert Pluim
2023-04-26 10:38 ` Eli Zaretskii
2023-04-26 11:47 ` Robert Pluim
2023-04-26 12:24 ` Eli Zaretskii
2023-04-26 14:27 ` Robert Pluim [this message]
2023-04-26 10:58 ` Vasilij Schneidermann
2023-04-26 10:56 ` Vasilij Schneidermann
2023-04-26 11:50 ` Robert Pluim
2023-04-26 14:31 ` Robert Pluim
2024-03-09 13:40 ` Vasilij Schneidermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkjasopn.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=62990@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mail@vasilij.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.