rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Doc: Update ulinks to RFC documents to avoid redirect 

The tools.ietf.org site has been decommissioned and replaced by a
number of sites serving various purposes.  Links to RFCs and BCPs
are now 301 redirected to their new respective IETF sites.  Since
this serves no purpose and only adds network overhead, update our
links to the new locations.

Backpatch to all supported versions.

Discussion: https://postgr.es/m/3C1CEA99-FCED-447D-9858-5A579B4C6687@yesql.se
Backpatch-through: v12
This commit is contained in:
Daniel Gustafsson 2024-04-10 13:53:25 +02:00
parent 01b55203ac
commit bfed705002
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/charset.sgml
View File

@ -834,7 +834,7 @@ CREATE COLLATION german (provider = libc, locale = 'de_DE');
See <ulink url="http://unicode.org/reports/tr35/tr35-collation.html">Unicode See <ulink url="http://unicode.org/reports/tr35/tr35-collation.html">Unicode
Technical Standard #35</ulink> Technical Standard #35</ulink>
and <ulink url="https://tools.ietf.org/html/bcp47">BCP 47</ulink> for and <ulink url="https://www.rfc-editor.org/info/bcp47">BCP 47</ulink> for
details. The list of possible collation types (<literal>co</literal> details. The list of possible collation types (<literal>co</literal>
subtag) can be found in subtag) can be found in
the <ulink url="https://github.com/unicode-org/cldr/blob/master/common/bcp47/collation.xml">CLDR the <ulink url="https://github.com/unicode-org/cldr/blob/master/common/bcp47/collation.xml">CLDR

4
doc/src/sgml/client-auth.sgml
View File

@ -1079,7 +1079,7 @@ omicron bryanh guest1
<para> <para>
The method <literal>scram-sha-256</literal> performs SCRAM-SHA-256 The method <literal>scram-sha-256</literal> performs SCRAM-SHA-256
authentication, as described in authentication, as described in
<ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>. It <ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>. It
is a challenge-response scheme that prevents password sniffing on is a challenge-response scheme that prevents password sniffing on
untrusted connections and supports storing passwords on the server in a untrusted connections and supports storing passwords on the server in a
cryptographically hashed form that is thought to be secure. cryptographically hashed form that is thought to be secure.
@ -1191,7 +1191,7 @@ omicron bryanh guest1
<para> <para>
<productname>GSSAPI</productname> is an industry-standard protocol <productname>GSSAPI</productname> is an industry-standard protocol
for secure authentication defined in for secure authentication defined in
<ulink url="https://tools.ietf.org/html/rfc2743">RFC 2743</ulink>. <ulink url="https://datatracker.ietf.org/doc/html/rfc2743">RFC 2743</ulink>.
<productname>PostgreSQL</productname> <productname>PostgreSQL</productname>
supports <productname>GSSAPI</productname> for authentication, supports <productname>GSSAPI</productname> for authentication,
communications encryption, or both. communications encryption, or both.

2
doc/src/sgml/json.sgml
View File

@ -13,7 +13,7 @@
<para> <para>
JSON data types are for storing JSON (JavaScript Object Notation) JSON data types are for storing JSON (JavaScript Object Notation)
data, as specified in <ulink url="https://tools.ietf.org/html/rfc7159">RFC data, as specified in <ulink url="https://datatracker.ietf.org/doc/html/rfc7159">RFC
7159</ulink>. Such data can also be stored as <type>text</type>, but 7159</ulink>. Such data can also be stored as <type>text</type>, but
the JSON data types have the advantage of enforcing that each the JSON data types have the advantage of enforcing that each
stored value is valid according to the JSON rules. There are also stored value is valid according to the JSON rules. There are also

2
doc/src/sgml/libpq.sgml
View File

@ -798,7 +798,7 @@ PGPing PQping(const char *conninfo);
connection parameters. There are two accepted formats for these strings: connection parameters. There are two accepted formats for these strings:
plain keyword/value strings plain keyword/value strings
and URIs. URIs generally follow and URIs. URIs generally follow
<ulink url="https://tools.ietf.org/html/rfc3986">RFC <ulink url="https://datatracker.ietf.org/doc/html/rfc3986">RFC
3986</ulink>, except that multi-host connection strings are allowed 3986</ulink>, except that multi-host connection strings are allowed
as further described below. as further described below.
</para> </para>

2
doc/src/sgml/ref/psql-ref.sgml
View File

@ -2710,7 +2710,7 @@ lo_import 152801
</indexterm> </indexterm>
writes column values separated by commas, applying the quoting writes column values separated by commas, applying the quoting
rules described in rules described in
<ulink url="https://tools.ietf.org/html/rfc4180">RFC 4180</ulink>. <ulink url="https://datatracker.ietf.org/doc/html/rfc4180">RFC 4180</ulink>.
This output is compatible with the CSV format of the server's This output is compatible with the CSV format of the server's
<command>COPY</command> command. <command>COPY</command> command.
A header line with column names is generated unless A header line with column names is generated unless