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 1miZFz-00030P-3A
	for pgsql-www@arkaria.postgresql.org; Thu, 04 Nov 2021 09:42:03 +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 1miZFx-0003E8-UU
	for pgsql-www@arkaria.postgresql.org; Thu, 04 Nov 2021 09:42:01 +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 1miZFx-0003Dz-MN
	for pgsql-www@lists.postgresql.org; Thu, 04 Nov 2021 09:42:01 +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 1miZFv-0002M8-4f
	for pgsql-www@lists.postgresql.org; Thu, 04 Nov 2021 09:42:00 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cmatte.me;
	s=myselector; t=1636018916;
	bh=CPIdCGNQY3K4ODnkTJ1F05d5A8MLAGMYX9UYEUVAGn4=;
	h=Date:To:From:Subject;
	b=nmpD8+BvizO+pz+0QMwcbtV0dXvVn4GOfzbhh1TJOw2oZjGtaD3SkO11tnu0CFNb9
	 cERMGh8ORVsZpmHBbRG2e9bcMPz7IvYmgLitY2TgcKobHtGDz63aIkKCWT/7J1G7J1
	 RdkeGgci96Jkh+0In7mVcycvJuvHwGU3VGH6A7S8rxdNhOCJuAKg3uLXDAWCh8wZzb
	 V7keLssHHN/pT3MnF9nz/JybPk8hwMmH3/IBfm24wzpb9/t4KHiZODIKjzSsOrIUUa
	 bYXDgIoc7SRQllnrUdKR7fVhHe3v6u1PbEJloF2mQ4guchePh9cDItKEo6jvLTl/sQ
	 9/1QKhPB0piFA==
Message-ID: <641bd039-a2e3-db73-dcc1-1b3d2707bfa9@cmatte.me>
Date: Thu, 4 Nov 2021 10:41:55 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.1
To: pgsql-www@lists.postgresql.org
Content-Language: en-US
From: =?UTF-8?Q?C=c3=a9lestin_Matte?= <celestin.matte@cmatte.me>
Subject: Issue report: search function not working for private lists
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/641bd039-a2e3-db73-dcc1-1b3d2707bfa9%40cmatte.me>
Precedence: bulk

There are several issues that prevent the correct installation of search functions for private lists:
- it is only possible to define a single archive search server in pgweb's settings.py, which makes it impossible to define both a public and a private archives server,
- there does not seem to be any kind of permissions verifications in pgweb/search/views.py that would allow only users subscribed to a list to search into it.

I've been told that this functionality did not indeed work for postresql.org's private lists.
-- 
Célestin Matte