custom-http-headers

[simonpoole]

While https://github.com/osmlab/editor-layer-index/issues/905 was closed, one point was raised by @rbuffat that the schema has a broken definition for the field. While the JSON spec doesn't rule out multiple objects with the same name https://datatracker.ietf.org/doc/html/rfc7159#section-4 (it is just a SHOULD not a MUST), in practice multiple values are not retrievable with any non-streaming parser that I know of.

The non-backwards compatible fix on the ELI side of things would be to modify the schema so that custom-http-headers is an array of the header objects and fixing up the couple of sources that use it. Alternatively (probably preferable) we should change the wording in the schema to allow just one header (which wouldn't impact anybody currently).