Skip to content

Commit 300d089

Browse files
committed
Fix contentEncoding RFC link
Signed-off-by: Juan Cruz Viotti <[email protected]>
1 parent 8bfa375 commit 300d089

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

content/2019-09/content/contentEncoding.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
keyword: "contentEncoding"
33
signature: "String"
4-
value: This keyword should be set to a standard (to increase interoperability) encoding name such as those defined in [RFC 4648](https://www.rfc-editor.org/info/rfc4686) and [RFC 2045](https://www.rfc-editor.org/info/rfc2045.html)
4+
value: This keyword should be set to a standard (to increase interoperability) encoding name such as those defined in [RFC 4648](https://www.rfc-editor.org/info/rfc4648) and [RFC 2045](https://www.rfc-editor.org/info/rfc2045.html)
55
summary: "The string instance should be interpreted as encoded binary data and decoded using the encoding named by this property."
66
kind: [ "annotation" ]
77
instance: [ "string" ]

content/2020-12/content/contentEncoding.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
keyword: "contentEncoding"
33
signature: "String"
4-
value: This keyword should be set to a standard (to increase interoperability) encoding name such as those defined in [RFC 4648](https://www.rfc-editor.org/info/rfc4686) and [RFC 2045](https://www.rfc-editor.org/info/rfc2045.html)
4+
value: This keyword should be set to a standard (to increase interoperability) encoding name such as those defined in [RFC 4648](https://www.rfc-editor.org/info/rfc4648) and [RFC 2045](https://www.rfc-editor.org/info/rfc2045.html)
55
summary: "The string instance should be interpreted as encoded binary data and decoded using the encoding named by this property."
66
kind: [ "annotation" ]
77
instance: [ "string" ]
@@ -65,7 +65,7 @@ header to
6565

6666
{{</learning-more>}}
6767

68-
[RFC 4648](https://datatracker.ietf.org/doc/html/rfc4686) _(The Base16, Base32,
68+
[RFC 4648](https://datatracker.ietf.org/doc/html/rfc4648) _(The Base16, Base32,
6969
and Base64 Data Encodings)_ and [RFC
7070
2045](https://datatracker.ietf.org/doc/html/rfc2045) _(Format of Internet
7171
Message Bodies)_ define the following standard encodings. In the interest of

content/draft7/validation/contentEncoding.markdown

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
keyword: "contentEncoding"
33
signature: "String"
4-
value: This keyword should be set to a standard (to increase interoperability) encoding name such as those defined in [RFC 4648](https://www.rfc-editor.org/info/rfc4686) and [RFC 2045](https://www.rfc-editor.org/info/rfc2045.html)
4+
value: This keyword should be set to a standard (to increase interoperability) encoding name such as those defined in [RFC 4648](https://www.rfc-editor.org/info/rfc4648) and [RFC 2045](https://www.rfc-editor.org/info/rfc2045.html)
55
summary: "The string instance should be interpreted as encoded binary data and decoded using the encoding named by this property."
66
kind: [ "annotation" ]
77
instance: [ "string" ]

0 commit comments

Comments
 (0)