Ticket #93 (closed editorial: fixed)
Repeating single-value header fields
|Reported by:||email@example.com||Owned by:||firstname.lastname@example.org|
|Component:||p1-messaging||Severity:||Active WG Document|
Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list [i.e., #(values)].
Now this seems to be kind of backwards, wouldn't it be *much* clearer if it said:
Multiple message-header fields with the same field-name MUST NOT be present in a message unless the entire field-value for that header field is defined as a comma-separated list [i.e., #(values)].
That being said, do we have a recommendation for recipients when that requirement is violated? I would assume that servers SHOULD return a 400 (Bad Request), but what about clients?
- Owner set to email@example.com
- Component set to messaging
- Priority set to normal
- Type changed from design to editorial
- Status changed from new to closed
- Resolution set to fixed