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

diff --git a/doc/src/sgml/acronyms.sgml b/doc/src/sgml/acronyms.sgml
index 2df6559accce57af2304f4a4cbef4b711c390275..159e600d726e57fc57c7934a20f8cf32f5c7fe1c 100644 (file)
--- a/doc/src/sgml/acronyms.sgml
+++ b/doc/src/sgml/acronyms.sgml
@@ -606,7 +606,7 @@
       
       url="https://en.wikipedia.org/wiki/Server_Name_Indication">
        Server Name Indication,
-      tools.ietf.org/html/rfc6066#section-3">RFC 6066
+      datatracker.ietf.org/doc/html/rfc6066#section-3">RFC 6066
      
     
    


diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml

index ddf4548828f4a3e31fa7d438e2b9afd7aa9027b2..5dc6a0a289d2e6c9299ceabf95636e2ceec29c59 100644 (file)

--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1624,7 +1624,7 @@ SCRAM-SHA-256$<iteration count>:&l
 
    where salt, StoredKey and
    ServerKey are in Base64 encoded format. This format is
-   the same as that specified by tools.ietf.org/html/rfc5803">RFC 5803.
+   the same as that specified by datatracker.ietf.org/doc/html/rfc5803">RFC 5803.
   
 
   


diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml

index 445fd175d8e63b703432138df387421c5761bc32..c152bd9306a22c5155879357b878a4dca2b131b0 100644 (file)

--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -939,7 +939,7 @@ CREATE COLLATION german (provider = libc, locale = 'de_DE');
 
     See Unicode
     Technical Standard #35
-    and tools.ietf.org/html/bcp47">BCP 47 for
+    and www.rfc-editor.org/info/bcp47">BCP 47 for
     details.  The list of possible collation types (co
     subtag) can be found in
     the CLDR
@@ -2723,7 +2723,7 @@ RESET client_encoding;
       
 
       
-       tools.ietf.org/html/rfc3629">RFC 3629
+       datatracker.ietf.org/doc/html/rfc3629">RFC 3629
 
        
         


diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml

index 68e73b9c328b7c2f9a8b6fcba41074dd1924db22..02fa1ecc752c7deb5c36c948bf48433b653fa0e5 100644 (file)

--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -627,7 +627,7 @@ hostnogssenc  database  user
        entire Distinguished Name (DN) of the certificate.
        This option is probably best used in conjunction with a username map.
        The comparison is done with the DN in
-       tools.ietf.org/html/rfc2253">RFC 2253
+       datatracker.ietf.org/doc/html/rfc2253">RFC 2253
        format. To see the DN of a client certificate
        in this format, do
 
@@ -977,7 +977,7 @@ omicron         bryanh                  guest1
      
       Ident authentication, which
       relies on an Identification Protocol
-      (tools.ietf.org/html/rfc1413">RFC 1413)
+      (datatracker.ietf.org/doc/html/rfc1413">RFC 1413)
       service on the client's machine.  (On local Unix-socket connections,
       this is treated as peer authentication.)
      
@@ -1116,7 +1116,7 @@ omicron         bryanh                  guest1
       
        The method scram-sha-256 performs SCRAM-SHA-256
        authentication, as described in
-       tools.ietf.org/html/rfc7677">RFC 7677.  It
+       datatracker.ietf.org/doc/html/rfc7677">RFC 7677.  It
        is a challenge-response scheme that prevents password sniffing on
        untrusted connections and supports storing passwords on the server in a
        cryptographically hashed form that is thought to be secure.
@@ -1228,7 +1228,7 @@ omicron         bryanh                  guest1
    
     GSSAPI is an industry-standard protocol
     for secure authentication defined in
-    tools.ietf.org/html/rfc2743">RFC 2743.
+    datatracker.ietf.org/doc/html/rfc2743">RFC 2743.
     PostgreSQL
     supports GSSAPI for authentication,
     communications encryption, or both.
@@ -1543,7 +1543,7 @@ omicron         bryanh                  guest1
 
    
     The Identification Protocol is described in
-    tools.ietf.org/html/rfc1413">RFC 1413.
+    datatracker.ietf.org/doc/html/rfc1413">RFC 1413.
     Virtually every Unix-like
     operating system ships with an ident server that listens on TCP
     port 113 by default. The basic functionality of an ident server
@@ -1712,7 +1712,7 @@ omicron         bryanh                  guest1
        
         Set to 1 to make the connection between PostgreSQL and the LDAP server
         use TLS encryption.  This uses the StartTLS
-        operation per tools.ietf.org/html/rfc4513">RFC 4513.
+        operation per datatracker.ietf.org/doc/html/rfc4513">RFC 4513.
         See also the ldapscheme option for an alternative.
        
       
@@ -1807,7 +1807,7 @@ omicron         bryanh                  guest1
        ldapurl
        
         
-         An tools.ietf.org/html/rfc4516">RFC 4516
+         An datatracker.ietf.org/doc/html/rfc4516">RFC 4516
          LDAP URL.  This is an alternative way to write some of the
          other LDAP options in a more compact and standard form.  The format is
 
@@ -1870,7 +1870,7 @@ ldap[s]://host[:port]/
      OpenLDAP as the LDAP client library, the
      ldapserver setting may be omitted.  In that case, a
      list of host names and ports is looked up via
-     tools.ietf.org/html/rfc2782">RFC 2782 DNS SRV records.
+     datatracker.ietf.org/doc/html/rfc2782">RFC 2782 DNS SRV records.
      The name _ldap._tcp.DOMAIN is looked up, where
      DOMAIN is extracted from ldapbasedn.
    


diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml

index 2fef3d37ed884c1371b3f94489d5c95fe4c320b4..8dac3086ca0413813b23fa97a4f11071bca8c024 100644 (file)

--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -2452,7 +2452,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
       the date and time.  PostgreSQL accepts that format on
       input, but on output it uses a space rather than T, as shown
       above.  This is for readability and for consistency with
-      tools.ietf.org/html/rfc3339">RFC 3339 as
+      datatracker.ietf.org/doc/html/rfc3339">RFC 3339 as
       well as some other database systems.
      
     
@@ -4348,7 +4348,7 @@ SELECT to_tsvector( 'postgraduate' ), to_tsquery( 'postgres:*' );
 
    
     The data type uuid stores Universally Unique Identifiers
-    (UUID) as defined by tools.ietf.org/html/rfc4122">RFC 4122,
+    (UUID) as defined by datatracker.ietf.org/doc/html/rfc4122">RFC 4122,
     ISO/IEC 9834-8:2005, and related standards.
     (Some systems refer to this data type as a globally unique identifier, or
     GUID,GUID instead.)  This


diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml

index d8fe3b29bcf97b671fbbf3f235cc64dfd67a75aa..34d6830b8b33d3824f9113d0d8d839cc731133ee 100644 (file)

--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -3279,7 +3279,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
            %z - is replaced by the time zone offset from
            UTC; a leading plus sign stands for east of UTC, a minus sign for
            west of UTC, hours and minutes follow with two digits each and no
-           delimiter between them (common form for tools.ietf.org/html/rfc822">RFC 822 date headers).
+           delimiter between them (common form for datatracker.ietf.org/doc/html/rfc822">RFC 822 date headers).
           
          
          


diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml

index 9603e81169ffe619c8c0eb4ead5ce64271a62e4f..57b3be9a64607170319f381ab102b7e2035fcd06 100644 (file)

--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4724,7 +4724,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
      
       
        The base64 format is that
-       of tools.ietf.org/html/rfc2045#section-6.8">RFC
+       of datatracker.ietf.org/doc/html/rfc2045#section-6.8">RFC
        2045 Section 6.8.  As per the RFC, encoded lines are
        broken at 76 characters.  However instead of the MIME CRLF
        end-of-line marker, only a newline is used for end-of-line.


diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml

index 4182d691d64014c3ca1c94fe6dd219fd53d98d57..d6de9120c0b1c4c0858c7eda7077f2e9be0419ac 100644 (file)

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


diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml

index 8b51d9ecc14b11b299823e804c78aac4b54d4868..997ae4f4038e0ea7ea769de091b803ba8549814e 100644 (file)

--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -873,7 +873,7 @@ PQsslKeyPassHook_OpenSSL_type PQgetSSLKeyPassHook_OpenSSL(void);
     connection parameters.  There are two accepted formats for these strings:
     plain keyword/value strings
     and URIs.  URIs generally follow
-    tools.ietf.org/html/rfc3986">RFC
+    datatracker.ietf.org/doc/html/rfc3986">RFC
     3986, except that multi-host connection strings are allowed
     as further described below.
    
@@ -958,7 +958,7 @@ postgresql:///mydb?host=localhost&port=5433
 
    
     The connection URI needs to be encoded with 
-    url="https://tools.ietf.org/html/rfc3986#section-2.1">percent-encoding
+    url="https://datatracker.ietf.org/doc/html/rfc3986#section-2.1">percent-encoding
     if it includes symbols with special meaning in any of its parts.  Here is
     an example where the equal sign (=) is replaced with
     %3D and the space character with
@@ -8236,7 +8236,7 @@ user=admin
    LDAP query will be performed. The result must be a list of
    keyword = value pairs which will be used to set
    connection options.  The URL must conform to
-   tools.ietf.org/html/rfc1959">RFC 1959
+   datatracker.ietf.org/doc/html/rfc1959">RFC 1959
    and be of the form
 
 ldap://[hostname[:port]]/search_base?attribute?search_scope?filter
@@ -8380,7 +8380,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
    
     For backward compatibility with earlier versions of PostgreSQL, the host
     IP address is verified in a manner different
-    from tools.ietf.org/html/rfc6125">RFC 6125.
+    from datatracker.ietf.org/doc/html/rfc6125">RFC 6125.
     The host IP address is always matched against dNSName
     SANs as well as iPAddress SANs, and can be matched
     against the Common Name attribute if no relevant SANs exist.


diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml

index 0d5c0e0b45bc7be7d7978af35b16dabd3572801c..3ca39c128a218cd8917b10a31541e7a14017907f 100644 (file)

--- a/doc/src/sgml/pgcrypto.sgml
+++ b/doc/src/sgml/pgcrypto.sgml
@@ -442,7 +442,7 @@ gen_salt(type text [, iter_count integer ]) returns text
 
   
    The functions here implement the encryption part of the OpenPGP
-   (tools.ietf.org/html/rfc4880">RFC 4880)
+   (datatracker.ietf.org/doc/html/rfc4880">RFC 4880)
    standard.  Supported are both symmetric-key and public-key encryption.
   
 


diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml

index ea314d279ac8e77db5e83bb9664887581483806e..70605dcb8827f982119aa81c1e9793d564c06085 100644 (file)

--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1585,7 +1585,7 @@ SELCT 1/0;
     respectively.  The frontend might close the connection at this point
     if it is dissatisfied with the response.  To continue after
     G, using the GSSAPI C bindings as discussed in
-    tools.ietf.org/html/rfc2744">RFC 2744
+    datatracker.ietf.org/doc/html/rfc2744">RFC 2744
     or equivalent, perform a GSSAPI initialization by
     calling gss_init_sec_context() in a loop and sending
     the result to the server, starting with an empty input and then with each
@@ -1722,8 +1722,8 @@ SELCT 1/0;
     The implemented SASL mechanisms at the moment
     are SCRAM-SHA-256 and its variant with channel
     binding SCRAM-SHA-256-PLUS. They are described in
-    detail in tools.ietf.org/html/rfc7677">RFC 7677
-    and tools.ietf.org/html/rfc5802">RFC 5802.
+    detail in datatracker.ietf.org/doc/html/rfc7677">RFC 7677
+    and datatracker.ietf.org/doc/html/rfc5802">RFC 5802.
    
 
    


diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml

index d4c8cafdba97a545813637c41b7a868a3b9b2502..9bdc0289fdbd9f2f7cec5816207ede5b5161c9e1 100644 (file)

--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -2919,7 +2919,7 @@ lo_import 152801
           
           writes column values separated by commas, applying the quoting
           rules described in
-          tools.ietf.org/html/rfc4180">RFC 4180.
+          datatracker.ietf.org/doc/html/rfc4180">RFC 4180.
           This output is compatible with the CSV format of the server's
           COPY command.
           A header line with column names is generated unless


diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml

index 1550be5695071bb8328a69700ad00648e7ae177d..94ac30059c3603e86251f977806c2e41184d4711 100644 (file)

--- a/doc/src/sgml/textsearch.sgml
+++ b/doc/src/sgml/textsearch.sgml
@@ -2218,7 +2218,7 @@ LIMIT 10;
 
    
     email does not support all valid email characters as
-    defined by tools.ietf.org/html/rfc5322">RFC 5322.
+    defined by datatracker.ietf.org/doc/html/rfc5322">RFC 5322.
     Specifically, the only non-alphanumeric characters supported for
     email user names are period, dash, and underscore.
    


diff --git a/doc/src/sgml/uuid-ossp.sgml b/doc/src/sgml/uuid-ossp.sgml

index 26bfb908daea184aaede42a7f6044e3e9da1cdc0..e20a2d6ea9ab1ecbf26296523a017a9d11d23d30 100644 (file)

--- a/doc/src/sgml/uuid-ossp.sgml
+++ b/doc/src/sgml/uuid-ossp.sgml
@@ -29,7 +29,7 @@
     shows the functions available to
    generate UUIDs.
    The relevant standards ITU-T Rec. X.667, ISO/IEC 9834-8:2005, and
-   tools.ietf.org/html/rfc4122">RFC 4122
+   datatracker.ietf.org/doc/html/rfc4122">RFC 4122
    specify four algorithms for generating UUIDs, identified by the
    version numbers 1, 3, 4, and 5.  (There is no version 2 algorithm.)
    Each of these algorithms could be suitable for a different set of

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index ddf4548828f4a3e31fa7d438e2b9afd7aa9027b2..5dc6a0a289d2e6c9299ceabf95636e2ceec29c59 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1624,7 +1624,7 @@ SCRAM-SHA-256$<iteration count>:&l
 
    where salt, StoredKey and
    ServerKey are in Base64 encoded format. This format is
-   the same as that specified by tools.ietf.org/html/rfc5803">RFC 5803.
+   the same as that specified by datatracker.ietf.org/doc/html/rfc5803">RFC 5803.
   
 
   

diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 445fd175d8e63b703432138df387421c5761bc32..c152bd9306a22c5155879357b878a4dca2b131b0 100644 (file)
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -939,7 +939,7 @@ CREATE COLLATION german (provider = libc, locale = 'de_DE');
 
     See Unicode
     Technical Standard #35
-    and tools.ietf.org/html/bcp47">BCP 47 for
+    and www.rfc-editor.org/info/bcp47">BCP 47 for
     details.  The list of possible collation types (co
     subtag) can be found in
     the CLDR
@@ -2723,7 +2723,7 @@ RESET client_encoding;
       
 
       
-       tools.ietf.org/html/rfc3629">RFC 3629
+       datatracker.ietf.org/doc/html/rfc3629">RFC 3629
 
        
         

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 68e73b9c328b7c2f9a8b6fcba41074dd1924db22..02fa1ecc752c7deb5c36c948bf48433b653fa0e5 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -627,7 +627,7 @@ hostnogssenc  database  user
        entire Distinguished Name (DN) of the certificate.
        This option is probably best used in conjunction with a username map.
        The comparison is done with the DN in
-       tools.ietf.org/html/rfc2253">RFC 2253
+       datatracker.ietf.org/doc/html/rfc2253">RFC 2253
        format. To see the DN of a client certificate
        in this format, do
 
@@ -977,7 +977,7 @@ omicron         bryanh                  guest1
      
       Ident authentication, which
       relies on an Identification Protocol
-      (tools.ietf.org/html/rfc1413">RFC 1413)
+      (datatracker.ietf.org/doc/html/rfc1413">RFC 1413)
       service on the client's machine.  (On local Unix-socket connections,
       this is treated as peer authentication.)
      
@@ -1116,7 +1116,7 @@ omicron         bryanh                  guest1
       
        The method scram-sha-256 performs SCRAM-SHA-256
        authentication, as described in
-       tools.ietf.org/html/rfc7677">RFC 7677.  It
+       datatracker.ietf.org/doc/html/rfc7677">RFC 7677.  It
        is a challenge-response scheme that prevents password sniffing on
        untrusted connections and supports storing passwords on the server in a
        cryptographically hashed form that is thought to be secure.
@@ -1228,7 +1228,7 @@ omicron         bryanh                  guest1
    
     GSSAPI is an industry-standard protocol
     for secure authentication defined in
-    tools.ietf.org/html/rfc2743">RFC 2743.
+    datatracker.ietf.org/doc/html/rfc2743">RFC 2743.
     PostgreSQL
     supports GSSAPI for authentication,
     communications encryption, or both.
@@ -1543,7 +1543,7 @@ omicron         bryanh                  guest1
 
    
     The Identification Protocol is described in
-    tools.ietf.org/html/rfc1413">RFC 1413.
+    datatracker.ietf.org/doc/html/rfc1413">RFC 1413.
     Virtually every Unix-like
     operating system ships with an ident server that listens on TCP
     port 113 by default. The basic functionality of an ident server
@@ -1712,7 +1712,7 @@ omicron         bryanh                  guest1
        
         Set to 1 to make the connection between PostgreSQL and the LDAP server
         use TLS encryption.  This uses the StartTLS
-        operation per tools.ietf.org/html/rfc4513">RFC 4513.
+        operation per datatracker.ietf.org/doc/html/rfc4513">RFC 4513.
         See also the ldapscheme option for an alternative.
        
       
@@ -1807,7 +1807,7 @@ omicron         bryanh                  guest1
        ldapurl
        
         
-         An tools.ietf.org/html/rfc4516">RFC 4516
+         An datatracker.ietf.org/doc/html/rfc4516">RFC 4516
          LDAP URL.  This is an alternative way to write some of the
          other LDAP options in a more compact and standard form.  The format is
 
@@ -1870,7 +1870,7 @@ ldap[s]://host[:port]/
      OpenLDAP as the LDAP client library, the
      ldapserver setting may be omitted.  In that case, a
      list of host names and ports is looked up via
-     tools.ietf.org/html/rfc2782">RFC 2782 DNS SRV records.
+     datatracker.ietf.org/doc/html/rfc2782">RFC 2782 DNS SRV records.
      The name _ldap._tcp.DOMAIN is looked up, where
      DOMAIN is extracted from ldapbasedn.
    

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 2fef3d37ed884c1371b3f94489d5c95fe4c320b4..8dac3086ca0413813b23fa97a4f11071bca8c024 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -2452,7 +2452,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
       the date and time.  PostgreSQL accepts that format on
       input, but on output it uses a space rather than T, as shown
       above.  This is for readability and for consistency with
-      tools.ietf.org/html/rfc3339">RFC 3339 as
+      datatracker.ietf.org/doc/html/rfc3339">RFC 3339 as
       well as some other database systems.
      
     
@@ -4348,7 +4348,7 @@ SELECT to_tsvector( 'postgraduate' ), to_tsquery( 'postgres:*' );
 
    
     The data type uuid stores Universally Unique Identifiers
-    (UUID) as defined by tools.ietf.org/html/rfc4122">RFC 4122,
+    (UUID) as defined by datatracker.ietf.org/doc/html/rfc4122">RFC 4122,
     ISO/IEC 9834-8:2005, and related standards.
     (Some systems refer to this data type as a globally unique identifier, or
     GUID,GUID instead.)  This

diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
index d8fe3b29bcf97b671fbbf3f235cc64dfd67a75aa..34d6830b8b33d3824f9113d0d8d839cc731133ee 100644 (file)
--- a/doc/src/sgml/ecpg.sgml
+++ b/doc/src/sgml/ecpg.sgml
@@ -3279,7 +3279,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
            %z - is replaced by the time zone offset from
            UTC; a leading plus sign stands for east of UTC, a minus sign for
            west of UTC, hours and minutes follow with two digits each and no
-           delimiter between them (common form for tools.ietf.org/html/rfc822">RFC 822 date headers).
+           delimiter between them (common form for datatracker.ietf.org/doc/html/rfc822">RFC 822 date headers).
           
          
          

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 9603e81169ffe619c8c0eb4ead5ce64271a62e4f..57b3be9a64607170319f381ab102b7e2035fcd06 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4724,7 +4724,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
      
       
        The base64 format is that
-       of tools.ietf.org/html/rfc2045#section-6.8">RFC
+       of datatracker.ietf.org/doc/html/rfc2045#section-6.8">RFC
        2045 Section 6.8.  As per the RFC, encoded lines are
        broken at 76 characters.  However instead of the MIME CRLF
        end-of-line marker, only a newline is used for end-of-line.

diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index 4182d691d64014c3ca1c94fe6dd219fd53d98d57..d6de9120c0b1c4c0858c7eda7077f2e9be0419ac 100644 (file)
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -13,7 +13,7 @@
 
  
   JSON data types are for storing JSON (JavaScript Object Notation)
-  data, as specified in tools.ietf.org/html/rfc7159">RFC
+  data, as specified in datatracker.ietf.org/doc/html/rfc7159">RFC
   7159. Such data can also be stored as text, but
   the JSON data types have the advantage of enforcing that each
   stored value is valid according to the JSON rules.  There are also

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 8b51d9ecc14b11b299823e804c78aac4b54d4868..997ae4f4038e0ea7ea769de091b803ba8549814e 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -873,7 +873,7 @@ PQsslKeyPassHook_OpenSSL_type PQgetSSLKeyPassHook_OpenSSL(void);
     connection parameters.  There are two accepted formats for these strings:
     plain keyword/value strings
     and URIs.  URIs generally follow
-    tools.ietf.org/html/rfc3986">RFC
+    datatracker.ietf.org/doc/html/rfc3986">RFC
     3986, except that multi-host connection strings are allowed
     as further described below.
    
@@ -958,7 +958,7 @@ postgresql:///mydb?host=localhost&port=5433
 
    
     The connection URI needs to be encoded with 
-    url="https://tools.ietf.org/html/rfc3986#section-2.1">percent-encoding
+    url="https://datatracker.ietf.org/doc/html/rfc3986#section-2.1">percent-encoding
     if it includes symbols with special meaning in any of its parts.  Here is
     an example where the equal sign (=) is replaced with
     %3D and the space character with
@@ -8236,7 +8236,7 @@ user=admin
    LDAP query will be performed. The result must be a list of
    keyword = value pairs which will be used to set
    connection options.  The URL must conform to
-   tools.ietf.org/html/rfc1959">RFC 1959
+   datatracker.ietf.org/doc/html/rfc1959">RFC 1959
    and be of the form
 
 ldap://[hostname[:port]]/search_base?attribute?search_scope?filter
@@ -8380,7 +8380,7 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
    
     For backward compatibility with earlier versions of PostgreSQL, the host
     IP address is verified in a manner different
-    from tools.ietf.org/html/rfc6125">RFC 6125.
+    from datatracker.ietf.org/doc/html/rfc6125">RFC 6125.
     The host IP address is always matched against dNSName
     SANs as well as iPAddress SANs, and can be matched
     against the Common Name attribute if no relevant SANs exist.


diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml

index 0d5c0e0b45bc7be7d7978af35b16dabd3572801c..3ca39c128a218cd8917b10a31541e7a14017907f 100644 (file)

--- a/doc/src/sgml/pgcrypto.sgml
+++ b/doc/src/sgml/pgcrypto.sgml
@@ -442,7 +442,7 @@ gen_salt(type text [, iter_count integer ]) returns text
 
   
    The functions here implement the encryption part of the OpenPGP
-   (tools.ietf.org/html/rfc4880">RFC 4880)
+   (datatracker.ietf.org/doc/html/rfc4880">RFC 4880)
    standard.  Supported are both symmetric-key and public-key encryption.
   
 


diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml

index ea314d279ac8e77db5e83bb9664887581483806e..70605dcb8827f982119aa81c1e9793d564c06085 100644 (file)

--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1585,7 +1585,7 @@ SELCT 1/0;
     respectively.  The frontend might close the connection at this point
     if it is dissatisfied with the response.  To continue after
     G, using the GSSAPI C bindings as discussed in
-    tools.ietf.org/html/rfc2744">RFC 2744
+    datatracker.ietf.org/doc/html/rfc2744">RFC 2744
     or equivalent, perform a GSSAPI initialization by
     calling gss_init_sec_context() in a loop and sending
     the result to the server, starting with an empty input and then with each
@@ -1722,8 +1722,8 @@ SELCT 1/0;
     The implemented SASL mechanisms at the moment
     are SCRAM-SHA-256 and its variant with channel
     binding SCRAM-SHA-256-PLUS. They are described in
-    detail in tools.ietf.org/html/rfc7677">RFC 7677
-    and tools.ietf.org/html/rfc5802">RFC 5802.
+    detail in datatracker.ietf.org/doc/html/rfc7677">RFC 7677
+    and datatracker.ietf.org/doc/html/rfc5802">RFC 5802.
    
 
    


diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml

index d4c8cafdba97a545813637c41b7a868a3b9b2502..9bdc0289fdbd9f2f7cec5816207ede5b5161c9e1 100644 (file)

--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -2919,7 +2919,7 @@ lo_import 152801
           
           writes column values separated by commas, applying the quoting
           rules described in
-          tools.ietf.org/html/rfc4180">RFC 4180.
+          datatracker.ietf.org/doc/html/rfc4180">RFC 4180.
           This output is compatible with the CSV format of the server's
           COPY command.
           A header line with column names is generated unless


diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml

index 1550be5695071bb8328a69700ad00648e7ae177d..94ac30059c3603e86251f977806c2e41184d4711 100644 (file)

--- a/doc/src/sgml/textsearch.sgml
+++ b/doc/src/sgml/textsearch.sgml
@@ -2218,7 +2218,7 @@ LIMIT 10;
 
    
     email does not support all valid email characters as
-    defined by tools.ietf.org/html/rfc5322">RFC 5322.
+    defined by datatracker.ietf.org/doc/html/rfc5322">RFC 5322.
     Specifically, the only non-alphanumeric characters supported for
     email user names are period, dash, and underscore.
    


diff --git a/doc/src/sgml/uuid-ossp.sgml b/doc/src/sgml/uuid-ossp.sgml

index 26bfb908daea184aaede42a7f6044e3e9da1cdc0..e20a2d6ea9ab1ecbf26296523a017a9d11d23d30 100644 (file)

--- a/doc/src/sgml/uuid-ossp.sgml
+++ b/doc/src/sgml/uuid-ossp.sgml
@@ -29,7 +29,7 @@
     shows the functions available to
    generate UUIDs.
    The relevant standards ITU-T Rec. X.667, ISO/IEC 9834-8:2005, and
-   tools.ietf.org/html/rfc4122">RFC 4122
+   datatracker.ietf.org/doc/html/rfc4122">RFC 4122
    specify four algorithms for generating UUIDs, identified by the
    version numbers 1, 3, 4, and 5.  (There is no version 2 algorithm.)
    Each of these algorithms could be suitable for a different set of

diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml
index 0d5c0e0b45bc7be7d7978af35b16dabd3572801c..3ca39c128a218cd8917b10a31541e7a14017907f 100644 (file)
--- a/doc/src/sgml/pgcrypto.sgml
+++ b/doc/src/sgml/pgcrypto.sgml
@@ -442,7 +442,7 @@ gen_salt(type text [, iter_count integer ]) returns text
 
   
    The functions here implement the encryption part of the OpenPGP
-   (tools.ietf.org/html/rfc4880">RFC 4880)
+   (datatracker.ietf.org/doc/html/rfc4880">RFC 4880)
    standard.  Supported are both symmetric-key and public-key encryption.
   
 

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index ea314d279ac8e77db5e83bb9664887581483806e..70605dcb8827f982119aa81c1e9793d564c06085 100644 (file)
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1585,7 +1585,7 @@ SELCT 1/0;
     respectively.  The frontend might close the connection at this point
     if it is dissatisfied with the response.  To continue after
     G, using the GSSAPI C bindings as discussed in
-    tools.ietf.org/html/rfc2744">RFC 2744
+    datatracker.ietf.org/doc/html/rfc2744">RFC 2744
     or equivalent, perform a GSSAPI initialization by
     calling gss_init_sec_context() in a loop and sending
     the result to the server, starting with an empty input and then with each
@@ -1722,8 +1722,8 @@ SELCT 1/0;
     The implemented SASL mechanisms at the moment
     are SCRAM-SHA-256 and its variant with channel
     binding SCRAM-SHA-256-PLUS. They are described in
-    detail in tools.ietf.org/html/rfc7677">RFC 7677
-    and tools.ietf.org/html/rfc5802">RFC 5802.
+    detail in datatracker.ietf.org/doc/html/rfc7677">RFC 7677
+    and datatracker.ietf.org/doc/html/rfc5802">RFC 5802.
    
 
    

diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
index d4c8cafdba97a545813637c41b7a868a3b9b2502..9bdc0289fdbd9f2f7cec5816207ede5b5161c9e1 100644 (file)
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ b/doc/src/sgml/ref/psql-ref.sgml
@@ -2919,7 +2919,7 @@ lo_import 152801
           
           writes column values separated by commas, applying the quoting
           rules described in
-          tools.ietf.org/html/rfc4180">RFC 4180.
+          datatracker.ietf.org/doc/html/rfc4180">RFC 4180.
           This output is compatible with the CSV format of the server's
           COPY command.
           A header line with column names is generated unless

diff --git a/doc/src/sgml/textsearch.sgml b/doc/src/sgml/textsearch.sgml
index 1550be5695071bb8328a69700ad00648e7ae177d..94ac30059c3603e86251f977806c2e41184d4711 100644 (file)
--- a/doc/src/sgml/textsearch.sgml
+++ b/doc/src/sgml/textsearch.sgml
@@ -2218,7 +2218,7 @@ LIMIT 10;
 
    
     email does not support all valid email characters as
-    defined by tools.ietf.org/html/rfc5322">RFC 5322.
+    defined by datatracker.ietf.org/doc/html/rfc5322">RFC 5322.
     Specifically, the only non-alphanumeric characters supported for
     email user names are period, dash, and underscore.
    

diff --git a/doc/src/sgml/uuid-ossp.sgml b/doc/src/sgml/uuid-ossp.sgml
index 26bfb908daea184aaede42a7f6044e3e9da1cdc0..e20a2d6ea9ab1ecbf26296523a017a9d11d23d30 100644 (file)
--- a/doc/src/sgml/uuid-ossp.sgml
+++ b/doc/src/sgml/uuid-ossp.sgml
@@ -29,7 +29,7 @@
     shows the functions available to
    generate UUIDs.
    The relevant standards ITU-T Rec. X.667, ISO/IEC 9834-8:2005, and
-   tools.ietf.org/html/rfc4122">RFC 4122
+   datatracker.ietf.org/doc/html/rfc4122">RFC 4122
    specify four algorithms for generating UUIDs, identified by the
    version numbers 1, 3, 4, and 5.  (There is no version 2 algorithm.)
    Each of these algorithms could be suitable for a different set of