Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit52b49b7

Browse files
Doc: Update ulinks to RFC documents to avoid redirect
The tools.ietf.org site has been decommissioned and replaced by anumber of sites serving various purposes. Links to RFCs and BCPsare now 301 redirected to their new respective IETF sites. Sincethis serves no purpose and only adds network overhead, update ourlinks to the new locations.Backpatch to all supported versions.Discussion:https://postgr.es/m/3C1CEA99-FCED-447D-9858-5A579B4C6687@yesql.seBackpatch-through: v12
1 parent5105c90 commit52b49b7

14 files changed

+30
-30
lines changed

‎doc/src/sgml/acronyms.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -634,7 +634,7 @@
634634
<ulink
635635
url="https://en.wikipedia.org/wiki/Server_Name_Indication">
636636
Server Name Indication</ulink>,
637-
<ulink url="https://tools.ietf.org/html/rfc6066#section-3">RFC 6066</ulink>
637+
<ulink url="https://datatracker.ietf.org/doc/html/rfc6066#section-3">RFC 6066</ulink>
638638
</para>
639639
</listitem>
640640
</varlistentry>

‎doc/src/sgml/catalogs.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1625,7 +1625,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
16251625
</synopsis>
16261626
where <replaceable>salt</replaceable>, <replaceable>StoredKey</replaceable> and
16271627
<replaceable>ServerKey</replaceable> are in Base64 encoded format. This format is
1628-
the same as that specified by <ulink url="https://tools.ietf.org/html/rfc5803">RFC 5803</ulink>.
1628+
the same as that specified by <ulink url="https://datatracker.ietf.org/doc/html/rfc5803">RFC 5803</ulink>.
16291629
</para>
16301630

16311631
<para>

‎doc/src/sgml/charset.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1702,7 +1702,7 @@ ORDER BY c COLLATE ebcdic;
17021702
</listitem>
17031703
<listitem>
17041704
<para>
1705-
<ulink url="https://tools.ietf.org/html/bcp47">BCP 47</ulink>
1705+
<ulink url="https://www.rfc-editor.org/info/bcp47">BCP 47</ulink>
17061706
</para>
17071707
</listitem>
17081708
<listitem>
@@ -3399,7 +3399,7 @@ RESET client_encoding;
33993399
</varlistentry>
34003400

34013401
<varlistentry>
3402-
<term><ulink url="https://tools.ietf.org/html/rfc3629">RFC 3629</ulink></term>
3402+
<term><ulink url="https://datatracker.ietf.org/doc/html/rfc3629">RFC 3629</ulink></term>
34033403

34043404
<listitem>
34053405
<para>

‎doc/src/sgml/client-auth.sgml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -691,7 +691,7 @@ include_dir <replaceable>directory</replaceable>
691691
entire <literal>Distinguished Name (DN)</literal> of the certificate.
692692
This option is probably best used in conjunction with a username map.
693693
The comparison is done with the <literal>DN</literal> in
694-
<ulink url="https://tools.ietf.org/html/rfc2253">RFC 2253</ulink>
694+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2253">RFC 2253</ulink>
695695
format. To see the <literal>DN</literal> of a client certificate
696696
in this format, do
697697
<programlisting>
@@ -1090,7 +1090,7 @@ omicron bryanh guest1
10901090
<para>
10911091
<link linkend="auth-ident">Ident authentication</link>, which
10921092
relies on an <quote>Identification Protocol</quote>
1093-
(<ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>)
1093+
(<ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>)
10941094
service on the client's machine. (On local Unix-socket connections,
10951095
this is treated as peer authentication.)
10961096
</para>
@@ -1229,7 +1229,7 @@ omicron bryanh guest1
12291229
<para>
12301230
The method <literal>scram-sha-256</literal> performs SCRAM-SHA-256
12311231
authentication, as described in
1232-
<ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>. It
1232+
<ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>. It
12331233
is a challenge-response scheme that prevents password sniffing on
12341234
untrusted connections and supports storing passwords on the server in a
12351235
cryptographically hashed form that is thought to be secure.
@@ -1336,7 +1336,7 @@ omicron bryanh guest1
13361336
<para>
13371337
<productname>GSSAPI</productname> is an industry-standard protocol
13381338
for secure authentication defined in
1339-
<ulink url="https://tools.ietf.org/html/rfc2743">RFC 2743</ulink>.
1339+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2743">RFC 2743</ulink>.
13401340
<productname>PostgreSQL</productname>
13411341
supports <productname>GSSAPI</productname> for authentication,
13421342
communications encryption, or both.
@@ -1651,7 +1651,7 @@ omicron bryanh guest1
16511651

16521652
<para>
16531653
The <quote>Identification Protocol</quote> is described in
1654-
<ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>.
1654+
<ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>.
16551655
Virtually every Unix-like
16561656
operating system ships with an ident server that listens on TCP
16571657
port 113 by default. The basic functionality of an ident server
@@ -1820,7 +1820,7 @@ omicron bryanh guest1
18201820
<para>
18211821
Set to 1 to make the connection between PostgreSQL and the LDAP server
18221822
use TLS encryption. This uses the <literal>StartTLS</literal>
1823-
operation per <ulink url="https://tools.ietf.org/html/rfc4513">RFC 4513</ulink>.
1823+
operation per <ulink url="https://datatracker.ietf.org/doc/html/rfc4513">RFC 4513</ulink>.
18241824
See also the <literal>ldapscheme</literal> option for an alternative.
18251825
</para>
18261826
</listitem>
@@ -1915,7 +1915,7 @@ omicron bryanh guest1
19151915
<term><literal>ldapurl</literal></term>
19161916
<listitem>
19171917
<para>
1918-
An <ulink url="https://tools.ietf.org/html/rfc4516">RFC 4516</ulink>
1918+
An <ulink url="https://datatracker.ietf.org/doc/html/rfc4516">RFC 4516</ulink>
19191919
LDAP URL. This is an alternative way to write some of the
19201920
other LDAP options in a more compact and standard form. The format is
19211921
<synopsis>
@@ -1978,7 +1978,7 @@ ldap[s]://<replaceable>host</replaceable>[:<replaceable>port</replaceable>]/<rep
19781978
<productname>OpenLDAP</productname> as the LDAP client library, the
19791979
<literal>ldapserver</literal> setting may be omitted. In that case, a
19801980
list of host names and ports is looked up via
1981-
<ulink url="https://tools.ietf.org/html/rfc2782">RFC 2782</ulink> DNS SRV records.
1981+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2782">RFC 2782</ulink> DNS SRV records.
19821982
The name <literal>_ldap._tcp.DOMAIN</literal> is looked up, where
19831983
<literal>DOMAIN</literal> is extracted from <literal>ldapbasedn</literal>.
19841984
</para>

‎doc/src/sgml/datatype.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2471,7 +2471,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
24712471
the date and time. <productname>PostgreSQL</productname> accepts that format on
24722472
input, but on output it uses a space rather than <literal>T</literal>, as shown
24732473
above. This is for readability and for consistency with
2474-
<ulink url="https://tools.ietf.org/html/rfc3339">RFC 3339</ulink> as
2474+
<ulink url="https://datatracker.ietf.org/doc/html/rfc3339">RFC 3339</ulink> as
24752475
well as some other database systems.
24762476
</para>
24772477
</note>
@@ -4367,7 +4367,7 @@ SELECT to_tsvector( 'postgraduate' ), to_tsquery( 'postgres:*' );
43674367

43684368
<para>
43694369
The data type <type>uuid</type> stores Universally Unique Identifiers
4370-
(UUID) as defined by <ulink url="https://tools.ietf.org/html/rfc4122">RFC 4122</ulink>,
4370+
(UUID) as defined by <ulink url="https://datatracker.ietf.org/doc/html/rfc4122">RFC 4122</ulink>,
43714371
ISO/IEC 9834-8:2005, and related standards.
43724372
(Some systems refer to this data type as a globally unique identifier, or
43734373
GUID,<indexterm><primary>GUID</primary></indexterm> instead.) This

‎doc/src/sgml/ecpg.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3317,7 +3317,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
33173317
<literal>%z</literal> - is replaced by the time zone offset from
33183318
UTC; a leading plus sign stands for east of UTC, a minus sign for
33193319
west of UTC, hours and minutes follow with two digits each and no
3320-
delimiter between them (common form for <ulink url="https://tools.ietf.org/html/rfc822">RFC 822</ulink> date headers).
3320+
delimiter between them (common form for <ulink url="https://datatracker.ietf.org/doc/html/rfc822">RFC 822</ulink> date headers).
33213321
</para>
33223322
</listitem>
33233323
<listitem>

‎doc/src/sgml/func.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4901,7 +4901,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
49014901
<listitem>
49024902
<para>
49034903
The <literal>base64</literal> format is that
4904-
of <ulink url="https://tools.ietf.org/html/rfc2045#section-6.8">RFC
4904+
of <ulink url="https://datatracker.ietf.org/doc/html/rfc2045#section-6.8">RFC
49054905
2045 Section 6.8</ulink>. As per the <acronym>RFC</acronym>, encoded lines are
49064906
broken at 76 characters. However instead of the MIME CRLF
49074907
end-of-line marker, only a newline is used for end-of-line.
@@ -14198,7 +14198,7 @@ CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple
1419814198
<function>uuid_extract_version</function> (uuid) <returnvalue>smallint</returnvalue>
1419914199
</synopsis>
1420014200
This function extracts the version from a UUID of the variant described by
14201-
<ulink url="https://tools.ietf.org/html/rfc4122">RFC 4122</ulink>. For
14201+
<ulink url="https://datatracker.ietf.org/doc/html/rfc4122">RFC 4122</ulink>. For
1420214202
other variants, this function returns null. For example, for a UUID
1420314203
generated by <function>gen_random_uuid</function>, this function will
1420414204
return 4.
@@ -15537,7 +15537,7 @@ table2-mapping
1553715537
values, with an additional SQL/JSON null value, and composite data structures
1553815538
that use JSON arrays and objects. The model is a formalization of the implied
1553915539
data model in the JSON specification
15540-
<ulink url="https://tools.ietf.org/html/rfc7159">RFC 7159</ulink>.
15540+
<ulink url="https://datatracker.ietf.org/doc/html/rfc7159">RFC 7159</ulink>.
1554115541
</para>
1554215542

1554315543
<para>

‎doc/src/sgml/json.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313

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

‎doc/src/sgml/libpq.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -920,7 +920,7 @@ PQsslKeyPassHook_OpenSSL_type PQgetSSLKeyPassHook_OpenSSL(void);
920920
connection parameters. There are two accepted formats for these strings:
921921
plain keyword/value strings
922922
and URIs. URIs generally follow
923-
<ulink url="https://tools.ietf.org/html/rfc3986">RFC
923+
<ulink url="https://datatracker.ietf.org/doc/html/rfc3986">RFC
924924
3986</ulink>, except that multi-host connection strings are allowed
925925
as further described below.
926926
</para>
@@ -1005,7 +1005,7 @@ postgresql:///mydb?host=localhost&amp;port=5433
10051005

10061006
<para>
10071007
The connection <acronym>URI</acronym> needs to be encoded with <ulink
1008-
url="https://tools.ietf.org/html/rfc3986#section-2.1">percent-encoding</ulink>
1008+
url="https://datatracker.ietf.org/doc/html/rfc3986#section-2.1">percent-encoding</ulink>
10091009
if it includes symbols with special meaning in any of its parts. Here is
10101010
an example where the equal sign (<literal>=</literal>) is replaced with
10111011
<literal>%3D</literal> and the space character with
@@ -9343,7 +9343,7 @@ user=admin
93439343
LDAP query will be performed. The result must be a list of
93449344
<literal>keyword = value</literal> pairs which will be used to set
93459345
connection options. The URL must conform to
9346-
<ulink url="https://tools.ietf.org/html/rfc1959">RFC 1959</ulink>
9346+
<ulink url="https://datatracker.ietf.org/doc/html/rfc1959">RFC 1959</ulink>
93479347
and be of the form
93489348
<synopsis>
93499349
ldap://[<replaceable>hostname</replaceable>[:<replaceable>port</replaceable>]]/<replaceable>search_base</replaceable>?<replaceable>attribute</replaceable>?<replaceable>search_scope</replaceable>?<replaceable>filter</replaceable>
@@ -9487,7 +9487,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
94879487
<para>
94889488
For backward compatibility with earlier versions of PostgreSQL, the host
94899489
IP address is verified in a manner different
9490-
from <ulink url="https://tools.ietf.org/html/rfc6125">RFC 6125</ulink>.
9490+
from <ulink url="https://datatracker.ietf.org/doc/html/rfc6125">RFC 6125</ulink>.
94919491
The host IP address is always matched against <literal>dNSName</literal>
94929492
SANs as well as <literal>iPAddress</literal> SANs, and can be matched
94939493
against the Common Name attribute if no relevant SANs exist.

‎doc/src/sgml/pgcrypto.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -442,7 +442,7 @@ gen_salt(type text [, iter_count integer ]) returns text
442442

443443
<para>
444444
The functions here implement the encryption part of the OpenPGP
445-
(<ulink url="https://tools.ietf.org/html/rfc4880">RFC 4880</ulink>)
445+
(<ulink url="https://datatracker.ietf.org/doc/html/rfc4880">RFC 4880</ulink>)
446446
standard. Supported are both symmetric-key and public-key encryption.
447447
</para>
448448

‎doc/src/sgml/protocol.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1600,7 +1600,7 @@ SELCT 1/0;<!-- this typo is intentional -->
16001600
respectively. The frontend might close the connection at this point
16011601
if it is dissatisfied with the response. To continue after
16021602
<literal>G</literal>, using the GSSAPI C bindings as discussed in
1603-
<ulink url="https://tools.ietf.org/html/rfc2744">RFC 2744</ulink>
1603+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2744">RFC 2744</ulink>
16041604
or equivalent, perform a <acronym>GSSAPI</acronym> initialization by
16051605
calling <function>gss_init_sec_context()</function> in a loop and sending
16061606
the result to the server, starting with an empty input and then with each
@@ -1737,8 +1737,8 @@ SELCT 1/0;<!-- this typo is intentional -->
17371737
The implemented SASL mechanisms at the moment
17381738
are <literal>SCRAM-SHA-256</literal> and its variant with channel
17391739
binding <literal>SCRAM-SHA-256-PLUS</literal>. They are described in
1740-
detail in <ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>
1741-
and <ulink url="https://tools.ietf.org/html/rfc5802">RFC 5802</ulink>.
1740+
detail in <ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>
1741+
and <ulink url="https://datatracker.ietf.org/doc/html/rfc5802">RFC 5802</ulink>.
17421742
</para>
17431743

17441744
<para>

‎doc/src/sgml/ref/psql-ref.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2983,7 +2983,7 @@ lo_import 152801
29832983
</indexterm>
29842984
writes column values separated by commas, applying the quoting
29852985
rules described in
2986-
<ulink url="https://tools.ietf.org/html/rfc4180">RFC 4180</ulink>.
2986+
<ulink url="https://datatracker.ietf.org/doc/html/rfc4180">RFC 4180</ulink>.
29872987
This output is compatible with the CSV format of the server's
29882988
<command>COPY</command> command.
29892989
A header line with column names is generated unless

‎doc/src/sgml/textsearch.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2221,7 +2221,7 @@ LIMIT 10;
22212221

22222222
<para>
22232223
<literal>email</literal> does not support all valid email characters as
2224-
defined by <ulink url="https://tools.ietf.org/html/rfc5322">RFC 5322</ulink>.
2224+
defined by <ulink url="https://datatracker.ietf.org/doc/html/rfc5322">RFC 5322</ulink>.
22252225
Specifically, the only non-alphanumeric characters supported for
22262226
email user names are period, dash, and underscore.
22272227
</para>

‎doc/src/sgml/uuid-ossp.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929
<xref linkend="uuid-ossp-functions"/> shows the functions available to
3030
generate UUIDs.
3131
The relevant standards ITU-T Rec. X.667, ISO/IEC 9834-8:2005, and
32-
<ulink url="https://tools.ietf.org/html/rfc4122">RFC 4122</ulink>
32+
<ulink url="https://datatracker.ietf.org/doc/html/rfc4122">RFC 4122</ulink>
3333
specify four algorithms for generating UUIDs, identified by the
3434
version numbers 1, 3, 4, and 5. (There is no version 2 algorithm.)
3535
Each of these algorithms could be suitable for a different set of

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp