Re: Issue report: search function not working for private lists

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
Cc: pgsql-www(at)lists(dot)postgresql(dot)org
Subject: Re: Issue report: search function not working for private lists
Date: 2021-11-04 10:25:57
Message-ID: CABUevEz4mvffKcrCuwH7=+JL6Z5HdvpQWOy+zA3NCNM+6653dA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Thu, Nov 4, 2021 at 10:42 AM Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
wrote:

> 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.
>

Yes, this is a known limitation. This is "documented" in a code comment:

def search(request):
if not settings.PUBLIC_ARCHIVES:
# We don't support searching of non-public archives at all at this
point.
# XXX: room for future improvement
return HttpResponseForbidden('Not public archives')

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2021-11-04 10:29:16 Re: [PATCHES] pglister: make organization name generic
Previous Message Magnus Hagander 2021-11-04 10:24:25 Re: [PATCH] pglister: Add possibility to override settings.py in settings_local.py