rfc8941v11.xml   rfc8941.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" conse nsus="true" docName="draft-ietf-httpbis-header-structure-19" indexInclude="true" ipr="trust200902" number="8941" prepTime="2021-01-12T23:21:01" scripts="Common, Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocIncl ude="true" xml:lang="en"> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" conse nsus="true" docName="draft-ietf-httpbis-header-structure-19" indexInclude="true" ipr="trust200902" number="8941" prepTime="2021-01-19T20:45:01" scripts="Common, Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocIncl ude="true" xml:lang="en">
<link href="https://datatracker.ietf.org/doc/draft-ietf-httpbis-header-structu re-19" rel="prev"/> <link href="https://datatracker.ietf.org/doc/draft-ietf-httpbis-header-structu re-19" rel="prev"/>
<link href="https://dx.doi.org/10.17487/rfc8941" rel="alternate"/> <link href="https://dx.doi.org/10.17487/rfc8941" rel="alternate"/>
<link href="urn:issn:2070-1721" rel="alternate"/> <link href="urn:issn:2070-1721" rel="alternate"/>
<front> <front>
<title>Structured Field Values for HTTP</title> <title>Structured Field Values for HTTP</title>
<seriesInfo name="RFC" value="8941" stream="IETF"/> <seriesInfo name="RFC" value="8941" stream="IETF"/>
<author initials="M." surname="Nottingham" fullname="Mark Nottingham"> <author initials="M." surname="Nottingham" fullname="Mark Nottingham">
<organization showOnFrontPage="true">Fastly</organization> <organization showOnFrontPage="true">Fastly</organization>
<address> <address>
<postal> <postal>
skipping to change at line 442 skipping to change at line 442
<name slugifiedName="name-lists">Lists</name> <name slugifiedName="name-lists">Lists</name>
<t indent="0" pn="section-3.1-1">Lists are arrays of zero or more member s, each of which can be an <t indent="0" pn="section-3.1-1">Lists are arrays of zero or more member s, each of which can be an
Item (<xref target="item" format="default" sectionFormat="of" derivedCont ent="Section 3.3"/>) or an Inner List (<xref target="inner-list" format="default " sectionFormat="of" derivedContent="Section 3.1.1"/>), both of which can be Item (<xref target="item" format="default" sectionFormat="of" derivedCont ent="Section 3.3"/>) or an Inner List (<xref target="inner-list" format="default " sectionFormat="of" derivedContent="Section 3.1.1"/>), both of which can be
Parameterized (<xref target="param" format="default" sectionFormat="of" d erivedContent="Section 3.1.2"/>).</t> Parameterized (<xref target="param" format="default" sectionFormat="of" d erivedContent="Section 3.1.2"/>).</t>
<t indent="0" pn="section-3.1-2">The ABNF for Lists in HTTP fields is:</ t> <t indent="0" pn="section-3.1-2">The ABNF for Lists in HTTP fields is:</ t>
<sourcecode type="abnf" markers="false" pn="section-3.1-3"> <sourcecode type="abnf" markers="false" pn="section-3.1-3">
sf-list = list-member *( OWS "," OWS list-member ) sf-list = list-member *( OWS "," OWS list-member )
list-member = sf-item / inner-list list-member = sf-item / inner-list
</sourcecode> </sourcecode>
<t indent="0" pn="section-3.1-4">Each member is separated by a comma and optional whitespace. For <t indent="0" pn="section-3.1-4">Each member is separated by a comma and optional whitespace. For
example, a field whose value is defined as a List of Strings could example, a field whose value is defined as a List of Tokens could
look like:</t> look like:</t>
<sourcecode type="http-message" markers="false" pn="section-3.1-5"> <sourcecode type="http-message" markers="false" pn="section-3.1-5">
Example-List: "foo", "bar", "It was the best of times." Example-List: sugar, tea, rum
</sourcecode> </sourcecode>
<t indent="0" pn="section-3.1-6">An empty List is denoted by not seriali zing the field at all. This <t indent="0" pn="section-3.1-6">An empty List is denoted by not seriali zing the field at all. This
implies that fields defined as Lists have a default empty value.</t> implies that fields defined as Lists have a default empty value.</t>
<t indent="0" pn="section-3.1-7">Note that Lists can have their members split across multiple lines <t indent="0" pn="section-3.1-7">Note that Lists can have their members split across multiple lines
of the same header or trailer section, as per <xref target="RFC7230" sect ion="3.2.2" format="default" sectionFormat="of" derivedLink="https://rfc-editor. org/rfc/rfc7230#section-3.2.2" derivedContent="RFC7230"/>; for example, the foll owing are of the same header or trailer section, as per <xref target="RFC7230" sect ion="3.2.2" format="default" sectionFormat="of" derivedLink="https://rfc-editor. org/rfc/rfc7230#section-3.2.2" derivedContent="RFC7230"/>; for example, the foll owing are
equivalent:</t> equivalent:</t>
<sourcecode type="http-message" markers="false" pn="section-3.1-8"> <sourcecode type="http-message" markers="false" pn="section-3.1-8">
Example-List: foo, bar Example-List: sugar, tea, rum
</sourcecode> </sourcecode>
<t indent="0" pn="section-3.1-9">and</t> <t indent="0" pn="section-3.1-9">and</t>
<sourcecode type="http-message" markers="false" pn="section-3.1-10"> <sourcecode type="http-message" markers="false" pn="section-3.1-10">
Example-List: foo Example-List: sugar, tea
Example-List: bar Example-List: rum
</sourcecode> </sourcecode>
<t indent="0" pn="section-3.1-11">However, individual members of a List cannot be safely split <t indent="0" pn="section-3.1-11">However, individual members of a List cannot be safely split
between lines; see <xref target="text-parse" format="default" sectionForm at="of" derivedContent="Section 4.2"/> between lines; see <xref target="text-parse" format="default" sectionForm at="of" derivedContent="Section 4.2"/>
for details.</t> for details.</t>
<t indent="0" pn="section-3.1-12">Parsers <bcp14>MUST</bcp14> support Li sts containing at least 1024 members. Field <t indent="0" pn="section-3.1-12">Parsers <bcp14>MUST</bcp14> support Li sts containing at least 1024 members. Field
specifications can constrain the types and cardinality of individual specifications can constrain the types and cardinality of individual
List values as they require.</t> List values as they require.</t>
<section anchor="inner-list" numbered="true" removeInRFC="false" toc="in clude" pn="section-3.1.1"> <section anchor="inner-list" numbered="true" removeInRFC="false" toc="in clude" pn="section-3.1.1">
<name slugifiedName="name-inner-lists">Inner Lists</name> <name slugifiedName="name-inner-lists">Inner Lists</name>
<t indent="0" pn="section-3.1.1-1">An Inner List is an array of zero o r more Items (<xref target="item" format="default" sectionFormat="of" derivedCon tent="Section 3.3"/>). Both the individual Items and the <t indent="0" pn="section-3.1.1-1">An Inner List is an array of zero o r more Items (<xref target="item" format="default" sectionFormat="of" derivedCon tent="Section 3.3"/>). Both the individual Items and the
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/