From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <matthieu@vs6975.lil01fr.vsys.cloud> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 16EE882F1 for <pve-devel@lists.proxmox.com>; Fri, 3 Mar 2023 12:22:47 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 011B0D719 for <pve-devel@lists.proxmox.com>; Fri, 3 Mar 2023 12:22:47 +0100 (CET) Received: from vs6975.lil01fr.vsys.cloud (vs6975.lil01fr.vsys.cloud [185.154.154.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Fri, 3 Mar 2023 12:22:45 +0100 (CET) Received: by vs6975.lil01fr.vsys.cloud (Postfix, from userid 1000) id B977A2075B; Fri, 3 Mar 2023 12:16:16 +0100 (CET) From: Matthieu Malvache <matthieu@ma2t.com> To: pve-devel@lists.proxmox.com Date: Fri, 3 Mar 2023 12:16:03 +0100 Message-Id: <20230303111604.2043-1-matthieu@ma2t.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% HEADER_FROM_DIFFERENT_DOMAINS 0.249 From and EnvelopeFrom 2nd level mail domains are different KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH container 0/1] Add support for custom timeout in vncproxy method X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 03 Mar 2023 11:22:47 -0000 Dear Maintainer, This patch adds support for a custom timeout value in the 'vncproxy' method of the Proxmox PVE REST API. The timeout can be specified using the 'timeout' parameter and defaults to 10 seconds if not set. The purpose of this change is to allow users to configure the timeout duration for the VNC proxy connection to better suit their needs. By default, the timeout is set to 10 seconds, which should work well for most use cases. However, some users may need to increase or decrease the timeout based on factors such as network latency. Thank you for considering this patch. Sincerely, Matthieu Malvache Matthieu Malvache (1): vnc: Allow custom timeout value in vncproxy method PVE/API2/Qemu.pm | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) -- 2.30.2