usefor-article-13 May 2004
[< Prev]
[TOC] [ Next >]
4.5. Size Limits
Compliant software MUST support headers of at least 998 octets, and
that is the only limit on the length of a header line prescribed by
this standard. However, specific rules to the contrary may apply in
particular cases (for example, according to [RFC 2047] header lines
containing encoded-words are limited to 76 octets).
NOTE: There is NO restriction on the number of lines into which
a header may be split, and hence there is NO restriction on the
total length of a header (in particular it may, by suitable
folding, be made to exceed the 998 octets restriction pertaining
to a single header line).
The syntax provides for the lines of a body to be up to 998 octets in
length, not including the CRLF. All software compliant with this
standard MUST support body lines of at least that length, and all
such software SHOULD support lines of arbitrary length. In
particular, relaying agents MUST transmit lines of arbitrary length
without truncation or any other modification.
NOTE: The limit of 998 octets is consistent with the
corresponding limit in [RFC 2822]. In practice, lines will be
much shorter, and [USEAGE] suggests a default limit of 79
characters to be used where there are no pressing needs to do
otherwise.
NOTE: This standard provides no upper bound on the overall size
of a single article, but neither does it forbid relaying agents
from dropping articles of excessive length. It is, however,
suggested that any limits thought appropriate by particular
agents would be more appropriately expressed in megabytes than
in kilobytes.
[< Prev]
[TOC] [ Next >]
#Diff to first older
--- ../usefor-article-12/Size_Limits.out November 2003
+++ ../usefor-article-13/Size_Limits.out May 2004
@@ -20,6 +20,7 @@
without truncation or any other modification.
+
NOTE: The limit of 998 octets is consistent with the
corresponding limit in [RFC 2822]. In practice, lines will be
much shorter, and [USEAGE] suggests a default limit of 79