Skip to content

prohibit vertical whitespace in field values (#377) #379

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Jun 11, 2020
Merged

prohibit vertical whitespace in field values (#377) #379

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3b49f05
restore changes from https://github.com/httpwg/http-core/commit/f20ca…
reschke Jun 3, 2020
5213b49
Merge branch 'master' into reschke-377
reschke Jun 4, 2020
759be43
Merge branch 'master' into reschke-377
reschke Jun 4, 2020
6b680c9
expand instructions from bare CR to any CTL (also, not to send alread…
reschke Jun 5, 2020
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
12 changes: 12 additions & 0 deletions draft-ietf-httpbis-semantics-latest.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1453,6 +1453,12 @@ Content-Type: text/plain
A recipient &SHOULD; treat other octets in field content (obs&nbhy;text) as
opaque data.
</t>
<t>
Field values containing control (<x:ref>CTL</x:ref>) characters such as
CR or LF are invalid; recipients &MUST; either reject a field value
containing control characters, or convert them to SP before processing or
forwarding the message.
</t>
<t>
Leading and trailing whitespace in raw field values is removed upon field
parsing (<xref target="field.parsing"/>). Field definitions where leading or trailing
Expand Down Expand Up @@ -12326,6 +12332,11 @@ Content-Encoding: gzip
Minimum URI lengths to be supported by implementations are now recommended.
(<xref target="resources"/>)
</t>
<t>
Clarify that control characters in field values are to be rejected or
mapped to SP.
(<xref target="field.values"/>)
</t>
<t>
The term "effective request URI" has been replaced with "target URI".
(<xref target="target.resource"/>)
Expand Down Expand Up @@ -12581,6 +12592,7 @@ Content-Encoding: gzip
<section title="Since draft-ietf-httpbis-semantics-08" anchor="changes.since.08">
<ul x:when-empty="None yet.">
<li>In <xref target="field.name.registry"/>, add optional "Comments" entry (<eref target="https://github.com/httpwg/http-core/issues/273"/>)</li>
<li>In <xref target="field.values"/>, instruct recipients how to deal with control characters in field values (<eref target="https://github.com/httpwg/http-core/issues/377"/>)</li>
<li>In <xref target="field.values"/>, update note about field ABNF (<eref target="https://github.com/httpwg/http-core/issues/380"/>)</li>
</ul>
</section>
Expand Down