From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 8DA661FF13B for ; Wed, 11 Mar 2026 16:02:04 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4A08D1F0D9; Wed, 11 Mar 2026 16:01:59 +0100 (CET) Date: Wed, 11 Mar 2026 16:01:49 +0100 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= Subject: applied-series: [PATCH proxmox{,-backup} 0/4] fix #3723: allow using node http proxy for remote connections To: Christian Ebner , pbs-devel@lists.proxmox.com References: <20260211161845.1006528-1-c.ebner@proxmox.com> In-Reply-To: <20260211161845.1006528-1-c.ebner@proxmox.com> MIME-Version: 1.0 User-Agent: astroid/0.17.0 (https://github.com/astroidmail/astroid) Message-Id: <1773241235.29r0k04i4f.astroid@yuna.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773241277864 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 5FHLQ65UZ2H2X4WFG3EGZAWHNACSZCSW X-Message-ID-Hash: 5FHLQ65UZ2H2X4WFG3EGZAWHNACSZCSW X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: with a small follow-up switching the precende in pbs-client around - since passing in an explicitly configured proxy is opt-in, it makes sense for that to take precedence over an env variable. On February 11, 2026 5:18 pm, Christian Ebner wrote: > These patches allow setting a boolean flag on a remote's > configuration to control whether or not to use the http proxy > settings of the Proxmox Backup Server node for the connection. >=20 > The default remains to not use the node's proxy, guaranteeing full > backwards compatibility. If no http proxy is configured, the flag has > no effect and no proxy will be used. >=20 > Currently it is only possible to set a custom per-remote proxy > setting, which can however be easily added on-demand. >=20 > Note: > Testing was performed using https://www.mitmproxy.org/ > Fingerprint on the PBS remote must then match the one provided by > the proxy, the proxy must be started with `--ssl-insecure` if > self-signed certificates are use on the remote. >=20 > Link to the issue in the bugtracker: > https://bugzilla.proxmox.com/show_bug.cgi?id=3D3723 >=20 >=20 > proxmox: >=20 > Christian Ebner (1): > pbs-api-types: remote: add flag to use node proxy for remote connect >=20 > pbs-api-types/src/remote.rs | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) >=20 >=20 > proxmox-backup: >=20 > Christian Ebner (3): > http client: use http proxy from client options if set > fix #3723: api: remote: optionally use node proxy config for http > client > ui: expose flag to use node's http proxy in remote edit window >=20 > pbs-client/src/http_client.rs | 9 +++++++++ > src/api2/config/remote.rs | 13 +++++++++++++ > src/config/node.rs | 5 +++++ > www/window/RemoteEdit.js | 19 +++++++++++++++++++ > 4 files changed, 46 insertions(+) >=20 >=20 > Summary over all repositories: > 5 files changed, 60 insertions(+), 0 deletions(-) >=20 > --=20 > Generated by murpp 0.9.0 >=20 >=20 >=20 >=20 >=20