Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constrain field combination to a section #469

Merged
merged 6 commits into from
Oct 29, 2020
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion draft-ietf-httpbis-semantics-latest.xml
Original file line number Diff line number Diff line change
Expand Up @@ -1451,9 +1451,11 @@ Content-Type: text/plain
<section title="Header Fields" anchor="header.fields">
<t>
<iref item="field"/>
<iref item="section"/>
HTTP messages use key/value pairs to convey data about the
message, its payload, the target resource, or the connection.
They are called "HTTP fields" or just "<x:dfn>fields</x:dfn>".
Fields occur in groups called "<x:dfn>field sections</x:dfn>" or just "sections".
</t>
<t>
<iref item="header section"/>
Expand Down Expand Up @@ -1541,7 +1543,7 @@ Content-Type: text/plain
duplicate header fields that would impact request processing.
</t>
<t>
A recipient &MAY; combine multiple field lines with the same field name
A recipient &MAY; combine multiple field lines within a field section that have the same field name
into one field line, without changing the semantics of the message, by
appending each subsequent field line value to the initial field line value
in order, separated by a comma and <x:ref>OWS</x:ref> (optional whitespace).
Expand Down Expand Up @@ -13382,6 +13384,7 @@ transfer-coding = &lt;transfer-coding, see <xref target="Messaging" x:fmt="," x:

<section title="Since draft-ietf-httpbis-semantics-12" anchor="changes.since.12">
<ul x:when-empty="None yet.">
<li>In <xref target="field-order"/>, constrain field combination to be within a section (<eref target="https://github.com/httpwg/http-core/issues/454"/>)</li>
</ul>
</section>
</section>
Expand Down