Date: Mon, 20 Jul 2020 15:39:50 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>,
	Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: Stale external URL in doc?
Message-ID: <20200720193950.GA1361@momjian.us>
References: <20200709.161226.204639179120026914.horikyota.ntt@gmail.com>
 <01C59535-7297-4E57-9A7C-D6E2D0E4851A@yesql.se>
 <1808659.1594302711@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1808659.1594302711@sss.pgh.pa.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Thu, Jul  9, 2020 at 09:51:51AM -0400, Tom Lane wrote:
> Daniel Gustafsson <daniel@yesql.se> writes:
> > As a short term fix we should either a) remove these links completely or b)
> > link to archived copies of the pages on archive.org; or c) find a more
> > appropriate pages to link to.  A quick search didn't turn up anything I would
> > prefer for (c), and I'm not sure what he legality of linking to a cached copy
> > is, so I would advocate for (a).
> 
> +1.  It should have been obvious just from the spelling of this URL that
> it wasn't intended to be a long term stable location.  Digging in the
> git history shows we've already updated it twice, and I wonder how many
> changes there were that we didn't notice.
> 
> Just reverting bbd3bdba3 seems appropriate to me.

Yes, I was keeping those URLs specifically to document intermediate
certificate usage, but now that we have documentation of how to set up
intermediates, we don't need it anymore.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee