well-typed/grapesy

Deal with duplicate header names for custom metadata

edsko opened this issue · 0 comments

edsko commented

The spec requires

Custom-Metadata header order is not guaranteed to be preserved except for values with duplicate header names. Duplicate header names may have their values joined with "," as the delimiter and be considered semantically equivalent. Implementations must split Binary-Headers on "," before decoding the Base64-encoded values.

We do not currently do this.