Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-www-owner+archive@lists.postgresql.org>)
	id 1mf1qB-0004xE-DR
	for pgsql-www@arkaria.postgresql.org; Mon, 25 Oct 2021 15:24:47 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-www-owner+archive@lists.postgresql.org>)
	id 1mf1qA-0005PZ-7b
	for pgsql-www@arkaria.postgresql.org; Mon, 25 Oct 2021 15:24:46 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <celestin.matte@cmatte.me>)
	id 1mf1qA-0005PQ-0E
	for pgsql-www@lists.postgresql.org; Mon, 25 Oct 2021 15:24:46 +0000
Received: from ploudseeker.com ([78.199.165.48])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <celestin.matte@cmatte.me>)
	id 1mf1q7-00013d-D8
	for pgsql-www@lists.postgresql.org; Mon, 25 Oct 2021 15:24:44 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cmatte.me;
	s=myselector; t=1635175480;
	bh=38feD76U2fD8pMLt5WbQwZIzdr9y+x1Dl7WGAUnO2t4=;
	h=Date:To:From:Subject;
	b=UQ2TcSsk2bScmpXLbXTVjXLZWu9bxJO/Wxjarn7xMkVWeTWgD9AyCyF29J+AcS24M
	 4DbuSb1BM8d4ywhUnEey9fmPRNJFGtVtWffmOpkRub+QZZP1q7QBESHmbqatCnI1VO
	 apxdlHXJ59WNYogtQO9WqZPbprWHQYs8alb8caD8GfswOJ6cIZByfYgmMPKvdKUll0
	 WxS10fJZKlpRHd0hkFNaPaPKPPtf60Tom64aG4VY8HtXR0BfM68zvM31lMN/IhEnVQ
	 /Fs0FJMMlARqCimXcap90wK5BTmL7uRXSmDbsoHf7EelJvqsxhPWPONaXD4cE6H06z
	 iq/gNuehgNb5Q==
Message-ID: <12a52385-ccd5-717d-1d3d-5748ed39f3bd@cmatte.me>
Date: Mon, 25 Oct 2021 17:24:39 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.0
To: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Content-Language: en-US
From: =?UTF-8?Q?C=c3=a9lestin_Matte?= <celestin.matte@cmatte.me>
Subject: [PATCH] pgarchives: Allow use of IP ranges for SEARCH_CLIENTS
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
List-Id: <pgsql-www.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-www@lists.postgresql.org>
List-Owner: <mailto:pgsql-www-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-www>
Archived-At: 
 <https://www.postgresql.org/message-id/12a52385-ccd5-717d-1d3d-5748ed39f3bd%40cmatte.me>
Precedence: bulk

Hello,

It's only possible to define single IP addresses in the SEARCH_CLIENTS directive (which defines who can use the search API). This patch allows to use IP ranges such as 0.0.0.0/0.
That said, now that I've understood that SEARCH_CLIENTS should contain pgweb server's IP address and not the end user's one, I'm not entirely sure this patch is useful.
It's up for discussion, then.

Cheers,
-- 
Célestin Matte