W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2022

Re: [Editorial Errata Reported] RFC7231 (6814)

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Mon, 10 Jan 2022 13:40:23 +0100
Message-ID: <c0fbb1f9-9815-c4e2-89cf-592797024860@greenbytes.de>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>, RFC Errata System <rfc-editor@rfc-editor.org>
Cc: 1736090121@qq.com, fielding@gbiv.com, ietf-http-wg@w3.org
Am 10.01.2022 um 13:27 schrieb Poul-Henning Kamp:
> --------
> RFC Errata System writes:
> 
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party
>> can log in to change the status and edit the report, if necessary.
> 
> FWIW:
> 
> I have a .txt downloaded June 7th 2014 where the TOC looks slightly weird there:
> 
>      |   7. Response Header Fields .........................................64|
>      |      7.1. Control Data ..............................................64|
>      |ed            7.1.1. Origination Date ...................................65|
>      |           7.1.2. Location ...........................................68|
>      |           7.1.3. Retry-After ........................................69|
> 
> (I added '|' chars added to mark begin and end of line)
> 
> The relevant bit in hexdump:
> 
>      000026f0  2e 2e 2e 2e 2e 2e 2e 2e  2e 36 34 0a 20 20 20 20  |.........64.    |
>      00002700  20 20 37 2e 31 2e 20 43  6f 6e 74 72 6f 6c 20 44  |  7.1. Control D|
>      00002710  61 74 61 20 2e 2e 2e 2e  2e 2e 2e 2e 2e 2e 2e 2e  |ata ............|
>      00002720  2e 2e 2e 2e 2e 2e 2e 2e  2e 2e 2e 2e 2e 2e 2e 2e  |................|
>      00002730  2e 2e 2e 2e 2e 2e 2e 2e  2e 2e 2e 2e 2e 2e 2e 2e  |................|
>      00002740  2e 2e 36 34 0a 65 64 20  20 20 20 20 20 20 20 20  |..64.ed         |
>      00002750  20 20 20 37 2e 31 2e 31  2e 20 4f 72 69 67 69 6e  |   7.1.1. Origin|
>      00002760  61 74 69 6f 6e 20 44 61  74 65 20 2e 2e 2e 2e 2e  |ation Date .....|
>      00002770  2e 2e 2e 2e 2e 2e 2e 2e  2e 2e 2e 2e 2e 2e 2e 2e  |................|
>      00002780  2e 2e 2e 2e 2e 2e 2e 2e  2e 2e 2e 2e 2e 2e 36 35  |..............65|
>      00002790  0a 20 20 20 20 20 20 20  20 20 20 20 37 2e 31 2e  |.           7.1.|
>      000027a0  32 2e 20 4c 6f 63 61 74  69 6f 6e 20 2e 2e 2e 2e  |2. Location ....|
> 
> I also have a rfc7231.xml downloaded December 8th 2016, but I dont know what to look for in it...

The bug was introduced by the RFC Editor *after* converting the XML; 
thus there's nothing to look for in the XML.

Best regards, Julian

-- 
<green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany
Amtsgericht Münster: HRB5782
Received on Monday, 10 January 2022 12:40:43 UTC

This archive was generated by hypermail 2.4.0 : Monday, 10 January 2022 12:40:44 UTC