Handling Long Lines in Content of Internet-Drafts and RFCs
RFC 8792
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-07-25
|
Amy Vezza | Downref to RFC 8792 approved by Last Call for draft-ietf-httpbis-digest-headers-13 |
2021-11-19
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2021-11-18
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2020-06-29
|
(System) | Received changes through RFC Editor sync (created alias RFC 8792, changed title to 'Handling Long Lines in Content of Internet-Drafts and RFCs', changed abstract … Received changes through RFC Editor sync (created alias RFC 8792, changed title to 'Handling Long Lines in Content of Internet-Drafts and RFCs', changed abstract to 'This document defines two strategies for handling long lines in width-bounded text content. One strategy, called the "single backslash" strategy, is based on the historical use of a single backslash ('\') character to indicate where line-folding has occurred, with the continuation occurring with the first character that is not a space character (' ') on the next line. The second strategy, called the "double backslash" strategy, extends the first strategy by adding a second backslash character to identify where the continuation begins and is thereby able to handle cases not supported by the first strategy. Both strategies use a self-describing header enabling automated reconstitution of the original content.', changed pages to 28, changed standardization level to Informational, changed state to RFC, added RFC published event at 2020-06-29, changed IESG state to RFC Published) |
2020-06-29
|
(System) | RFC published |