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

Commit0a97ef7

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 parent4f90750 commit0a97ef7

File tree

6 files changed

+8
-8
lines changed

6 files changed

+8
-8
lines changed

‎doc/src/sgml/charset.sgml

Lines changed: 1 addition & 1 deletion
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

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1079,7 +1079,7 @@ omicron bryanh guest1
10791079
<para>
10801080
The method <literal>scram-sha-256</literal> performs SCRAM-SHA-256
10811081
authentication, as described in
1082-
<ulink url="https://tools.ietf.org/html/rfc7677">RFC 7677</ulink>. It
1082+
<ulink url="https://datatracker.ietf.org/doc/html/rfc7677">RFC 7677</ulink>. It
10831083
is a challenge-response scheme that prevents password sniffing on
10841084
untrusted connections and supports storing passwords on the server in a
10851085
cryptographically hashed form that is thought to be secure.
@@ -1191,7 +1191,7 @@ omicron bryanh guest1
11911191
<para>
11921192
<productname>GSSAPI</productname> is an industry-standard protocol
11931193
for secure authentication defined in
1194-
<ulink url="https://tools.ietf.org/html/rfc2743">RFC 2743</ulink>.
1194+
<ulink url="https://datatracker.ietf.org/doc/html/rfc2743">RFC 2743</ulink>.
11951195
<productname>PostgreSQL</productname>
11961196
supports <productname>GSSAPI</productname> for authentication,
11971197
communications encryption, or both.

‎doc/src/sgml/func.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4450,7 +4450,7 @@ SELECT format('Testing %3$s, %2$s, %s', 'one', 'two', 'three');
44504450
<listitem>
44514451
<para>
44524452
The <literal>base64</literal> format is that
4453-
of <ulink url="https://tools.ietf.org/html/rfc2045#section-6.8">RFC
4453+
of <ulink url="https://datatracker.ietf.org/doc/html/rfc2045#section-6.8">RFC
44544454
2045 Section 6.8</ulink>. As per the RFC, encoded lines are
44554455
broken at 76 characters. However instead of the MIME CRLF
44564456
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: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -867,7 +867,7 @@ PQsslKeyPassHook_OpenSSL_type PQgetSSLKeyPassHook_OpenSSL(void);
867867
connection parameters. There are two accepted formats for these strings:
868868
plain keyword/value strings
869869
and URIs. URIs generally follow
870-
<ulink url="https://tools.ietf.org/html/rfc3986">RFC
870+
<ulink url="https://datatracker.ietf.org/doc/html/rfc3986">RFC
871871
3986</ulink>, except that multi-host connection strings are allowed
872872
as further described below.
873873
</para>
@@ -952,7 +952,7 @@ postgresql:///mydb?host=localhost&amp;port=5433
952952

953953
<para>
954954
The connection <acronym>URI</acronym> needs to be encoded with <ulink
955-
url="https://tools.ietf.org/html/rfc3986#section-2.1">percent-encoding</ulink>
955+
url="https://datatracker.ietf.org/doc/html/rfc3986#section-2.1">percent-encoding</ulink>
956956
if it includes symbols with special meaning in any of its parts. Here is
957957
an example where the equal sign (<literal>=</literal>) is replaced with
958958
<literal>%3D</literal> and the space character with

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

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

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp