From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pbs-devel-bounces@lists.proxmox.com>
Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40])
	by lore.proxmox.com (Postfix) with ESMTPS id E7A291FF146
	for <inbox@lore.proxmox.com>; Tue, 21 Jul 2026 10:20:57 +0200 (CEST)
Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1])
	by gate001.proxmox.com (Proxmox) with ESMTP id 079D9214AE;
	Tue, 21 Jul 2026 10:20:57 +0200 (CEST)
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Tue, 21 Jul 2026 10:20:50 +0200
Message-Id: <DK43PW51PHRP.2VKPBHWVSHDM@proxmox.com>
Subject: Re: [PATCH proxmox{,-backup} 0/3] add flag to opt-in using node
 proxy config for s3 connections
From: "Shan Shaji" <s.shaji@proxmox.com>
To: "Christian Ebner" <c.ebner@proxmox.com>, <pbs-devel@lists.proxmox.com>
X-Mailer: aerc 0.20.0
References: <20260511151924.901315-1-c.ebner@proxmox.com>
 <2052bff9-73d8-4cee-9a80-1d93c6dd6996@proxmox.com>
In-Reply-To: <2052bff9-73d8-4cee-9a80-1d93c6dd6996@proxmox.com>
X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2
X-Bm-Transport-Timestamp: 1784622025165
X-SPAM-LEVEL: Spam detection results:  0
	AWL                     0.155 Adjusted score from AWL reputation of From:
 address
	DMARC_MISSING             0.1 Missing DMARC policy
	KAM_DMARC_STATUS         0.01 Test Rule for DKIM or SPF Failure with Strict
 Alignment (newer systems)
	RCVD_IN_DNSWL_LOW        -0.7 Sender listed at https://www.dnswl.org/,
 low trust
	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: MDDVJ7GCFR6WE6OIGFTI66VP3XZO76XR
X-Message-ID-Hash: MDDVJ7GCFR6WE6OIGFTI66VP3XZO76XR
X-MailFrom: s.shaji@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
 <pbs-devel.lists.proxmox.com>
List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pbs-devel-owner@lists.proxmox.com>
List-Post: <mailto:pbs-devel@lists.proxmox.com>
List-Subscribe: <mailto:pbs-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pbs-devel-leave@lists.proxmox.com>

Hi,=20

I have also did a round of testing using the tinyproxy and everything works=
 fine.
The s3 client only uses the proxy when the flag is enabled.=20

Tested-by: Shan Shaji <s.shaji@proxmox.com>

On Mon Jul 20, 2026 at 3:08 PM CEST, Christian Ebner wrote:
> On 5/11/26 5:17 PM, Christian Ebner wrote:
>> Currently, if set the node proxy config is used unconditionally also
>> for S3 client API connections. Since this is however not always the
>> intention, allow users to expliciteley opt-in for individual S3
>> endpoint configurations.
>>=20
>> Reported in the community forum:
>> https://forum.proxmox.com/threads/183436/
>
> gentle ping since the status of this patches was requested in the=20
> enterprise support.