From: "Shan Shaji" <s.shaji@proxmox.com>
To: "Christian Ebner" <c.ebner@proxmox.com>, <pbs-devel@lists.proxmox.com>
Subject: Re: [PATCH proxmox{,-backup} 0/3] add flag to opt-in using node proxy config for s3 connections
Date: Tue, 21 Jul 2026 10:20:50 +0200 [thread overview]
Message-ID: <DK43PW51PHRP.2VKPBHWVSHDM@proxmox.com> (raw)
In-Reply-To: <2052bff9-73d8-4cee-9a80-1d93c6dd6996@proxmox.com>
Hi,
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.
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.
>>
>> Reported in the community forum:
>> https://forum.proxmox.com/threads/183436/
>
> gentle ping since the status of this patches was requested in the
> enterprise support.
next prev parent reply other threads:[~2026-07-21 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 15:19 [PATCH proxmox{,-backup} 0/3] add flag to opt-in using node proxy config for s3 connections Christian Ebner
2026-05-11 15:19 ` [PATCH proxmox 1/3] s3-client: add flag to opt-in for using node proxy for connections Christian Ebner
2026-05-11 15:19 ` [PATCH proxmox-backup 2/3] api: config: allow editing the use-node-config flag for s3 endpoints Christian Ebner
2026-05-11 15:19 ` [PATCH proxmox-backup 3/3] ui: add opt-in flag for using the node proxy config for s3 connections Christian Ebner
2026-07-20 13:08 ` [PATCH proxmox{,-backup} 0/3] add flag to opt-in using " Christian Ebner
2026-07-21 8:20 ` Shan Shaji [this message]
2026-07-21 5:45 ` Robert Obkircher
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=DK43PW51PHRP.2VKPBHWVSHDM@proxmox.com \
--to=s.shaji@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-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