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

Commitf6dcddf

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 parentbf1cfe7 commitf6dcddf

File tree

14 files changed

+29
-29
lines changed

14 files changed

+29
-29
lines changed

‎doc/src/sgml/acronyms.sgml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -625,7 +625,7 @@
625625
<ulink
626626
url="https://en.wikipedia.org/wiki/Server_Name_Indication">
627627
Server Name Indication</ulink>,
628-
<ulink url="https://tools.ietf.org/html/rfc6066#section-3">RFC 6066</ulink>
628+
<ulink url="https://datatracker.ietf.org/doc/html/rfc6066#section-3">RFC 6066</ulink>
629629
</para>
630630
</listitem>
631631
</varlistentry>

‎doc/src/sgml/catalogs.sgml‎

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

16301630
<para>

‎doc/src/sgml/charset.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1603,7 +1603,7 @@ ORDER BY c COLLATE ebcdic;
16031603
</listitem>
16041604
<listitem>
16051605
<para>
1606-
<ulink url="https://tools.ietf.org/html/bcp47">BCP 47</ulink>
1606+
<ulink url="https://www.rfc-editor.org/info/bcp47">BCP 47</ulink>
16071607
</para>
16081608
</listitem>
16091609
<listitem>
@@ -3300,7 +3300,7 @@ RESET client_encoding;
33003300
</varlistentry>
33013301

33023302
<varlistentry>
3303-
<term><ulink url="https://tools.ietf.org/html/rfc3629">RFC 3629</ulink></term>
3303+
<term><ulink url="https://datatracker.ietf.org/doc/html/rfc3629">RFC 3629</ulink></term>
33043304

33053305
<listitem>
33063306
<para>

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -662,7 +662,7 @@ include_dir <replaceable>directory</replaceable>
662662
entire <literal>Distinguished Name (DN)</literal> of the certificate.
663663
This option is probably best used in conjunction with a username map.
664664
The comparison is done with the <literal>DN</literal> in
665-
<ulink url="https://tools.ietf.org/html/rfc2253">RFC 2253</ulink>
665+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2253">RFC 2253</ulink>
666666
format. To see the <literal>DN</literal> of a client certificate
667667
in this format, do
668668
<programlisting>
@@ -1089,7 +1089,7 @@ omicron bryanh guest1
10891089
<para>
10901090
<link linkend="auth-ident">Ident authentication</link>, which
10911091
relies on an <quote>Identification Protocol</quote>
1092-
(<ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>)
1092+
(<ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>)
10931093
service on the client's machine. (On local Unix-socket connections,
10941094
this is treated as peer authentication.)
10951095
</para>
@@ -1228,7 +1228,7 @@ omicron bryanh guest1
12281228
<para>
12291229
The method <literal>scram-sha-256</literal> performs SCRAM-SHA-256
12301230
authentication, as described in
1231-
<ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>. It
1231+
<ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>. It
12321232
is a challenge-response scheme that prevents password sniffing on
12331233
untrusted connections and supports storing passwords on the server in a
12341234
cryptographically hashed form that is thought to be secure.
@@ -1340,7 +1340,7 @@ omicron bryanh guest1
13401340
<para>
13411341
<productname>GSSAPI</productname> is an industry-standard protocol
13421342
for secure authentication defined in
1343-
<ulink url="https://tools.ietf.org/html/rfc2743">RFC 2743</ulink>.
1343+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2743">RFC 2743</ulink>.
13441344
<productname>PostgreSQL</productname>
13451345
supports <productname>GSSAPI</productname> for authentication,
13461346
communications encryption, or both.
@@ -1655,7 +1655,7 @@ omicron bryanh guest1
16551655

16561656
<para>
16571657
The <quote>Identification Protocol</quote> is described in
1658-
<ulink url="https://tools.ietf.org/html/rfc1413">RFC 1413</ulink>.
1658+
<ulink url="https://datatracker.ietf.org/doc/html/rfc1413">RFC 1413</ulink>.
16591659
Virtually every Unix-like
16601660
operating system ships with an ident server that listens on TCP
16611661
port 113 by default. The basic functionality of an ident server
@@ -1824,7 +1824,7 @@ omicron bryanh guest1
18241824
<para>
18251825
Set to 1 to make the connection between PostgreSQL and the LDAP server
18261826
use TLS encryption. This uses the <literal>StartTLS</literal>
1827-
operation per <ulink url="https://tools.ietf.org/html/rfc4513">RFC 4513</ulink>.
1827+
operation per <ulink url="https://datatracker.ietf.org/doc/html/rfc4513">RFC 4513</ulink>.
18281828
See also the <literal>ldapscheme</literal> option for an alternative.
18291829
</para>
18301830
</listitem>
@@ -1919,7 +1919,7 @@ omicron bryanh guest1
19191919
<term><literal>ldapurl</literal></term>
19201920
<listitem>
19211921
<para>
1922-
An <ulink url="https://tools.ietf.org/html/rfc4516">RFC 4516</ulink>
1922+
An <ulink url="https://datatracker.ietf.org/doc/html/rfc4516">RFC 4516</ulink>
19231923
LDAP URL. This is an alternative way to write some of the
19241924
other LDAP options in a more compact and standard form. The format is
19251925
<synopsis>
@@ -1982,7 +1982,7 @@ ldap[s]://<replaceable>host</replaceable>[:<replaceable>port</replaceable>]/<rep
19821982
<productname>OpenLDAP</productname> as the LDAP client library, the
19831983
<literal>ldapserver</literal> setting may be omitted. In that case, a
19841984
list of host names and ports is looked up via
1985-
<ulink url="https://tools.ietf.org/html/rfc2782">RFC 2782</ulink> DNS SRV records.
1985+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2782">RFC 2782</ulink> DNS SRV records.
19861986
The name <literal>_ldap._tcp.DOMAIN</literal> is looked up, where
19871987
<literal>DOMAIN</literal> is extracted from <literal>ldapbasedn</literal>.
19881988
</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
@@ -3316,7 +3316,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
33163316
<literal>%z</literal> - is replaced by the time zone offset from
33173317
UTC; a leading plus sign stands for east of UTC, a minus sign for
33183318
west of UTC, hours and minutes follow with two digits each and no
3319-
delimiter between them (common form for <ulink url="https://tools.ietf.org/html/rfc822">RFC 822</ulink> date headers).
3319+
delimiter between them (common form for <ulink url="https://datatracker.ietf.org/doc/html/rfc822">RFC 822</ulink> date headers).
33203320
</para>
33213321
</listitem>
33223322
<listitem>

‎doc/src/sgml/func.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4783,7 +4783,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
47834783
<listitem>
47844784
<para>
47854785
The <literal>base64</literal> format is that
4786-
of <ulink url="https://tools.ietf.org/html/rfc2045#section-6.8">RFC
4786+
of <ulink url="https://datatracker.ietf.org/doc/html/rfc2045#section-6.8">RFC
47874787
2045 Section 6.8</ulink>. As per the <acronym>RFC</acronym>, encoded lines are
47884788
broken at 76 characters. However instead of the MIME CRLF
47894789
end-of-line marker, only a newline is used for end-of-line.
@@ -15268,7 +15268,7 @@ table2-mapping
1526815268
values, with an additional SQL/JSON null value, and composite data structures
1526915269
that use JSON arrays and objects. The model is a formalization of the implied
1527015270
data model in the JSON specification
15271-
<ulink url="https://tools.ietf.org/html/rfc7159">RFC 7159</ulink>.
15271+
<ulink url="https://datatracker.ietf.org/doc/html/rfc7159">RFC 7159</ulink>.
1527215272
</para>
1527315273

1527415274
<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
@@ -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
@@ -8561,7 +8561,7 @@ user=admin
85618561
LDAP query will be performed. The result must be a list of
85628562
<literal>keyword = value</literal> pairs which will be used to set
85638563
connection options. The URL must conform to
8564-
<ulink url="https://tools.ietf.org/html/rfc1959">RFC 1959</ulink>
8564+
<ulink url="https://datatracker.ietf.org/doc/html/rfc1959">RFC 1959</ulink>
85658565
and be of the form
85668566
<synopsis>
85678567
ldap://[<replaceable>hostname</replaceable>[:<replaceable>port</replaceable>]]/<replaceable>search_base</replaceable>?<replaceable>attribute</replaceable>?<replaceable>search_scope</replaceable>?<replaceable>filter</replaceable>
@@ -8705,7 +8705,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
87058705
<para>
87068706
For backward compatibility with earlier versions of PostgreSQL, the host
87078707
IP address is verified in a manner different
8708-
from <ulink url="https://tools.ietf.org/html/rfc6125">RFC 6125</ulink>.
8708+
from <ulink url="https://datatracker.ietf.org/doc/html/rfc6125">RFC 6125</ulink>.
87098709
The host IP address is always matched against <literal>dNSName</literal>
87108710
SANs as well as <literal>iPAddress</literal> SANs, and can be matched
87118711
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

0 commit comments

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