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

Commit2e56ad6

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 parent7fe32ea commit2e56ad6

14 files changed

+27
-27
lines changed

‎doc/src/sgml/acronyms.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -606,7 +606,7 @@
606606
<ulink
607607
url="https://en.wikipedia.org/wiki/Server_Name_Indication">
608608
Server Name Indication</ulink>,
609-
<ulink url="https://tools.ietf.org/html/rfc6066#section-3">RFC 6066</ulink>
609+
<ulink url="https://datatracker.ietf.org/doc/html/rfc6066#section-3">RFC 6066</ulink>
610610
</para>
611611
</listitem>
612612
</varlistentry>

‎doc/src/sgml/catalogs.sgml

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

16201620
<para>

‎doc/src/sgml/charset.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -836,7 +836,7 @@ CREATE COLLATION german (provider = libc, locale = 'de_DE');
836836

837837
See <ulink url="https://www.unicode.org/reports/tr35/tr35-collation.html">Unicode
838838
Technical Standard #35</ulink>
839-
and <ulink url="https://tools.ietf.org/html/bcp47">BCP 47</ulink> for
839+
and <ulink url="https://www.rfc-editor.org/info/bcp47">BCP 47</ulink> for
840840
details. The list of possible collation types (<literal>co</literal>
841841
subtag) can be found in
842842
the <ulink url="https://github.com/unicode-org/cldr/blob/master/common/bcp47/collation.xml">CLDR
@@ -2620,7 +2620,7 @@ RESET client_encoding;
26202620
</varlistentry>
26212621

26222622
<varlistentry>
2623-
<term><ulink url="https://tools.ietf.org/html/rfc3629">RFC 3629</ulink></term>
2623+
<term><ulink url="https://datatracker.ietf.org/doc/html/rfc3629">RFC 3629</ulink></term>
26242624

26252625
<listitem>
26262626
<para>

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -627,7 +627,7 @@ hostnogssenc <replaceable>database</replaceable> <replaceable>user</replaceabl
627627
entire <literal>Distinguished Name (DN)</literal> of the certificate.
628628
This option is probably best used in conjunction with a username map.
629629
The comparison is done with the <literal>DN</literal> in
630-
<ulink url="https://tools.ietf.org/html/rfc2253">RFC 2253</ulink>
630+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2253">RFC 2253</ulink>
631631
format. To see the <literal>DN</literal> of a client certificate
632632
in this format, do
633633
<programlisting>
@@ -967,7 +967,7 @@ omicron bryanh guest1
967967
<para>
968968
<link linkend="auth-ident">Ident authentication</link>, which
969969
relies on an <quote>Identification Protocol</quote>
970-
(<ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>)
970+
(<ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>)
971971
service on the client's machine. (On local Unix-socket connections,
972972
this is treated as peer authentication.)
973973
</para>
@@ -1106,7 +1106,7 @@ omicron bryanh guest1
11061106
<para>
11071107
The method <literal>scram-sha-256</literal> performs SCRAM-SHA-256
11081108
authentication, as described in
1109-
<ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>. It
1109+
<ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>. It
11101110
is a challenge-response scheme that prevents password sniffing on
11111111
untrusted connections and supports storing passwords on the server in a
11121112
cryptographically hashed form that is thought to be secure.
@@ -1218,7 +1218,7 @@ omicron bryanh guest1
12181218
<para>
12191219
<productname>GSSAPI</productname> is an industry-standard protocol
12201220
for secure authentication defined in
1221-
<ulink url="https://tools.ietf.org/html/rfc2743">RFC 2743</ulink>.
1221+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2743">RFC 2743</ulink>.
12221222
<productname>PostgreSQL</productname>
12231223
supports <productname>GSSAPI</productname> for authentication,
12241224
communications encryption, or both.
@@ -1533,7 +1533,7 @@ omicron bryanh guest1
15331533

15341534
<para>
15351535
The <quote>Identification Protocol</quote> is described in
1536-
<ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>.
1536+
<ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>.
15371537
Virtually every Unix-like
15381538
operating system ships with an ident server that listens on TCP
15391539
port 113 by default. The basic functionality of an ident server
@@ -1702,7 +1702,7 @@ omicron bryanh guest1
17021702
<para>
17031703
Set to 1 to make the connection between PostgreSQL and the LDAP server
17041704
use TLS encryption. This uses the <literal>StartTLS</literal>
1705-
operation per <ulink url="https://tools.ietf.org/html/rfc4513">RFC 4513</ulink>.
1705+
operation per <ulink url="https://datatracker.ietf.org/doc/html/rfc4513">RFC 4513</ulink>.
17061706
See also the <literal>ldapscheme</literal> option for an alternative.
17071707
</para>
17081708
</listitem>
@@ -1797,7 +1797,7 @@ omicron bryanh guest1
17971797
<term><literal>ldapurl</literal></term>
17981798
<listitem>
17991799
<para>
1800-
An <ulink url="https://tools.ietf.org/html/rfc4516">RFC 4516</ulink>
1800+
An <ulink url="https://datatracker.ietf.org/doc/html/rfc4516">RFC 4516</ulink>
18011801
LDAP URL. This is an alternative way to write some of the
18021802
other LDAP options in a more compact and standard form. The format is
18031803
<synopsis>
@@ -1860,7 +1860,7 @@ ldap[s]://<replaceable>host</replaceable>[:<replaceable>port</replaceable>]/<rep
18601860
<productname>OpenLDAP</productname> as the LDAP client library, the
18611861
<literal>ldapserver</literal> setting may be omitted. In that case, a
18621862
list of host names and ports is looked up via
1863-
<ulink url="https://tools.ietf.org/html/rfc2782">RFC 2782</ulink> DNS SRV records.
1863+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2782">RFC 2782</ulink> DNS SRV records.
18641864
The name <literal>_ldap._tcp.DOMAIN</literal> is looked up, where
18651865
<literal>DOMAIN</literal> is extracted from <literal>ldapbasedn</literal>.
18661866
</para>

‎doc/src/sgml/datatype.sgml

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

43064306
<para>
43074307
The data type <type>uuid</type> stores Universally Unique Identifiers
4308-
(UUID) as defined by <ulink url="https://tools.ietf.org/html/rfc4122">RFC 4122</ulink>,
4308+
(UUID) as defined by <ulink url="https://datatracker.ietf.org/doc/html/rfc4122">RFC 4122</ulink>,
43094309
ISO/IEC 9834-8:2005, and related standards.
43104310
(Some systems refer to this data type as a globally unique identifier, or
43114311
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
@@ -3279,7 +3279,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
32793279
<literal>%z</literal> - is replaced by the time zone offset from
32803280
UTC; a leading plus sign stands for east of UTC, a minus sign for
32813281
west of UTC, hours and minutes follow with two digits each and no
3282-
delimiter between them (common form for <ulink url="https://tools.ietf.org/html/rfc822">RFC 822</ulink> date headers).
3282+
delimiter between them (common form for <ulink url="https://datatracker.ietf.org/doc/html/rfc822">RFC 822</ulink> date headers).
32833283
</para>
32843284
</listitem>
32853285
<listitem>

‎doc/src/sgml/func.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4573,7 +4573,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
45734573
<listitem>
45744574
<para>
45754575
The <literal>base64</literal> format is that
4576-
of <ulink url="https://tools.ietf.org/html/rfc2045#section-6.8">RFC
4576+
of <ulink url="https://datatracker.ietf.org/doc/html/rfc2045#section-6.8">RFC
45774577
2045 Section 6.8</ulink>. As per the <acronym>RFC</acronym>, encoded lines are
45784578
broken at 76 characters. However instead of the MIME CRLF
45794579
end-of-line marker, only a newline is used for end-of-line.

‎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: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -873,7 +873,7 @@ PQsslKeyPassHook_OpenSSL_type PQgetSSLKeyPassHook_OpenSSL(void);
873873
connection parameters. There are two accepted formats for these strings:
874874
plain keyword/value strings
875875
and URIs. URIs generally follow
876-
<ulink url="https://tools.ietf.org/html/rfc3986">RFC
876+
<ulink url="https://datatracker.ietf.org/doc/html/rfc3986">RFC
877877
3986</ulink>, except that multi-host connection strings are allowed
878878
as further described below.
879879
</para>
@@ -958,7 +958,7 @@ postgresql:///mydb?host=localhost&amp;port=5433
958958

959959
<para>
960960
The connection <acronym>URI</acronym> needs to be encoded with <ulink
961-
url="https://tools.ietf.org/html/rfc3986#section-2.1">percent-encoding</ulink>
961+
url="https://datatracker.ietf.org/doc/html/rfc3986#section-2.1">percent-encoding</ulink>
962962
if it includes symbols with special meaning in any of its parts. Here is
963963
an example where the equal sign (<literal>=</literal>) is replaced with
964964
<literal>%3D</literal> and the space character with
@@ -8215,7 +8215,7 @@ user=admin
82158215
LDAP query will be performed. The result must be a list of
82168216
<literal>keyword = value</literal> pairs which will be used to set
82178217
connection options. The URL must conform to
8218-
<ulink url="https://tools.ietf.org/html/rfc1959">RFC 1959</ulink>
8218+
<ulink url="https://datatracker.ietf.org/doc/html/rfc1959">RFC 1959</ulink>
82198219
and be of the form
82208220
<synopsis>
82218221
ldap://[<replaceable>hostname</replaceable>[:<replaceable>port</replaceable>]]/<replaceable>search_base</replaceable>?<replaceable>attribute</replaceable>?<replaceable>search_scope</replaceable>?<replaceable>filter</replaceable>

‎doc/src/sgml/pgcrypto.sgml

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

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

‎doc/src/sgml/protocol.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1585,7 +1585,7 @@ SELCT 1/0;<!-- this typo is intentional -->
15851585
respectively. The frontend might close the connection at this point
15861586
if it is dissatisfied with the response. To continue after
15871587
<literal>G</literal>, using the GSSAPI C bindings as discussed in
1588-
<ulink url="https://tools.ietf.org/html/rfc2744">RFC 2744</ulink>
1588+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2744">RFC 2744</ulink>
15891589
or equivalent, perform a <acronym>GSSAPI</acronym> initialization by
15901590
calling <function>gss_init_sec_context()</function> in a loop and sending
15911591
the result to the server, starting with an empty input and then with each
@@ -1722,8 +1722,8 @@ ErrorMessage.
17221722
The implemented SASL mechanisms at the moment
17231723
are <literal>SCRAM-SHA-256</literal> and its variant with channel
17241724
binding <literal>SCRAM-SHA-256-PLUS</literal>. They are described in
1725-
detail in <ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>
1726-
and <ulink url="https://tools.ietf.org/html/rfc5802">RFC 5802</ulink>.
1725+
detail in <ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>
1726+
and <ulink url="https://datatracker.ietf.org/doc/html/rfc5802">RFC 5802</ulink>.
17271727
</para>
17281728

17291729
<para>

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2876,7 +2876,7 @@ lo_import 152801
28762876
</indexterm>
28772877
writes column values separated by commas, applying the quoting
28782878
rules described in
2879-
<ulink url="https://tools.ietf.org/html/rfc4180">RFC 4180</ulink>.
2879+
<ulink url="https://datatracker.ietf.org/doc/html/rfc4180">RFC 4180</ulink>.
28802880
This output is compatible with the CSV format of the server's
28812881
<command>COPY</command> command.
28822882
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
@@ -2218,7 +2218,7 @@ LIMIT 10;
22182218

22192219
<para>
22202220
<literal>email</literal> does not support all valid email characters as
2221-
defined by <ulink url="https://tools.ietf.org/html/rfc5322">RFC 5322</ulink>.
2221+
defined by <ulink url="https://datatracker.ietf.org/doc/html/rfc5322">RFC 5322</ulink>.
22222222
Specifically, the only non-alphanumeric characters supported for
22232223
email user names are period, dash, and underscore.
22242224
</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