From 07d99dc2e197f62df113e2796bfae48637cba098 Mon Sep 17 00:00:00 2001 From: Nigel Tao Date: Thu, 12 Mar 2020 16:58:38 +1100 Subject: [PATCH] Update some RFC links --- doc/spec/rac-spec.md | 6 +++--- std/json/decode_json.wuffs | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/spec/rac-spec.md b/doc/spec/rac-spec.md index da6bd57f..94a457d4 100644 --- a/doc/spec/rac-spec.md +++ b/doc/spec/rac-spec.md @@ -8,10 +8,10 @@ Status: Draft (as of September 2019). There is no compatibility guarantee yet. RAC is a *compressed* file format that allows *random access* (not just sequential access) to the decompressed contents. In comparison to some other popular compression formats, all four of the -[Zlib](https://tools.ietf.org/html/rfc1950), -[Brotli](https://tools.ietf.org/html/rfc7932), +[Zlib](https://www.ietf.org/rfc/rfc1950.txt), +[Brotli](https://www.ietf.org/rfc/rfc7932.txt), [LZ4](https://github.com/lz4/lz4/blob/master/doc/lz4_Frame_format.md) and -[Zstandard](https://tools.ietf.org/html/rfc8478) specifications explicitly +[Zstandard](https://www.ietf.org/rfc/rfc8478.txt) specifications explicitly contain the identical phrase: "the data format defined by this specification does not attempt to allow random access to compressed data". diff --git a/std/json/decode_json.wuffs b/std/json/decode_json.wuffs index 194cfcbe..36aa2dbe 100644 --- a/std/json/decode_json.wuffs +++ b/std/json/decode_json.wuffs @@ -33,8 +33,8 @@ pub struct decoder? implements base.token_decoder( // maximum is 1024 (stack is 1024 bits or 128 bytes), also known as // decoder_depth_max_incl. // - // The [JSON spec](https://tools.ietf.org/html/rfc7159) clearly states, "an - // implementation may set limits on the maximum depth of nesting". + // The [JSON spec](https://www.ietf.org/rfc/rfc8259.txt) clearly states, + // "an implementation may set limits on the maximum depth of nesting". // // In comparison, as of February 2020, the Chromium web browser's JSON // parser's maximum recursion depth is 200: