public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
	"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-http-server v2 1/1] fix unexpected EOF for client when closing TLS session
Date: Tue, 8 Apr 2025 11:00:57 +0200	[thread overview]
Message-ID: <d455e8a8-363a-4e44-81b8-c0fb1f9f1027@proxmox.com> (raw)
In-Reply-To: <1603485978.1040.1744102131292@webmail.proxmox.com>

Am 08.04.25 um 10:48 schrieb Fabian Grünbichler:
>> Fiona Ebner <f.ebner@proxmox.com> hat am 08.04.2025 09:27 CEST geschrieben:
>> I feel like the questions regarding blocking/missing client ack from
>> Fabian from v1 are not answered yet:
>>
>>> If I read the docs right, this could block (would that be an issue here?) and could potentially destroy the handle (so that might need to be rechecked afterwards to prevent spurious warnings?)
>>>
>>> what happens if we initiate the teardown, and the client never acks it?
> 
> there was some more input in a separate mail:
> 
> https://lore.proxmox.com/pve-devel/mailman.799.1741211155.293.pve-devel@lists.proxmox.com/

Okay, great :)

It would be nice if mailman (or something) wouldn't mess up
mails/threads from external senders :/


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

      reply	other threads:[~2025-04-08  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250305214447.128975-1-admin@truthsolo.net>
2025-03-05 21:45 ` Rob Rozestraten via pve-devel
2025-04-07 19:49   ` [pve-devel] applied: " Thomas Lamprecht
2025-04-08  7:27   ` [pve-devel] " Fiona Ebner
2025-04-08  8:48     ` Fabian Grünbichler
2025-04-08  9:00       ` Fiona Ebner [this message]

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=d455e8a8-363a-4e44-81b8-c0fb1f9f1027@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal