summaryrefslogtreecommitdiff
path: root/doc/src/sgml/json.sgml
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-08-17 11:39:00 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-08-17 11:47:43 -0400
commitca49d69b7c8f04c495ce39ff4460e017656db901 (patch)
tree4f979967a1b6ed027346dedbead32ab31bbca4f6 /doc/src/sgml/json.sgml
parentb469387fc09a00e1ea9c7e010fafdcf117299cad (diff)
doc: Update RFC URLs
Consistently use the IETF HTML links instead of a random mix of different sites and formats. Correct one RFC number and fix one broken link.
Diffstat (limited to 'doc/src/sgml/json.sgml')
-rw-r--r--doc/src/sgml/json.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/json.sgml b/doc/src/sgml/json.sgml
index 3cf78d6394c..7dfdf967645 100644
--- a/doc/src/sgml/json.sgml
+++ b/doc/src/sgml/json.sgml
@@ -13,7 +13,7 @@
<para>
JSON data types are for storing JSON (JavaScript Object Notation)
- data, as specified in <ulink url="http://rfc7159.net/rfc7159">RFC
+ data, as specified in <ulink url="https://tools.ietf.org/html/rfc7159">RFC
7159</ulink>. Such data can also be stored as <type>text</type>, but
the JSON data types have the advantage of enforcing that each
stored value is valid according to the JSON rules. There are also