Repository navigation
[v0.3] specify order for fields#get, fields#set #792
Description
For the operations on a fields resource that set or get all values of a named field, the specification should indicate their order; is it serialization order?
Also, what does it mean actually for a name to have multiple values? For HTTP/1.1, would that correspond to multiple Name: Value lines? That is my assumption but it might be good to spell it out somehow.
Activity
pchickey commentedon Aug 29, 2025
We have left the order unspecified to give implementations flexibility, in many implementations it may not be possible to control order (e.g. whatwg fetch).
Yes, in 1.1 multiple values corresponds to multiple Name: Value lines, I don't recall offhand where the 2 and 3 specs spell out how it works in those but we can point to those.
lann commentedon Sep 2, 2025
HTTP semantics allows reordering (by e.g. proxies, but seems applicable here). One subtlety there is that two fields with the same key can't be reordered relative to each other.