From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 44EC21FF146 for ; Tue, 07 Jul 2026 14:47:35 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 65AC721438; Tue, 07 Jul 2026 14:47:34 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com, David Riley Subject: applied: [PATCH pve-manager v3] api: sdn: fix trailing slashes in delete requests Date: Tue, 7 Jul 2026 14:47:17 +0200 Message-ID: <178342843173.85077.7765786434213775133.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260428122156.82218-1-d.riley@proxmox.com> References: <20260428122156.82218-1-d.riley@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1783428443799 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.033 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) 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: I4XN5O3KTLPFZSY3P3GOGIXZ5UCS6XY4 X-Message-ID-Hash: I4XN5O3KTLPFZSY3P3GOGIXZ5UCS6XY4 X-MailFrom: f.ebner@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 VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 28 Apr 2026 14:21:56 +0200, David Riley wrote: > Fixes delete request containing double slashes (//), resulting in a > URI like `/sdn/dns//`. Although this gets normalized on the > server, a strict firewall/proxy might cause problems. > > According to RFC 2396, a path may only consist of a > single slash [0]. Applied, thanks! [1/1] api: sdn: fix trailing slashes in delete requests commit: bdb81246ae9d4283e6eeae555c15812bee2e4bf9