Headers order and using same header multiple times

[honzajavorek]

According to documentation at https://github.com/apiaryio/blueprint-transactions, transaction objects contain HTTP headers for both requests and responses as key-value mappings (objects). This could lead to problems with headers of the same name:

Content-Type: text/plain
Set-Cookie: key1=sample content 1
Set-Cookie: key2=sample content 2
Set-Cookie: key3=sample content 3

vs.

Content-Type: text/plain
Set-Cookie: key1=sample content 1; key2=sample content 2; key3=sample content 3

---

I did not test the behavior and I did not bump into any problems with it. I just spotted this possible flaw when reading documentation and I wanted to point it out. This problem should be verified first.

[netmilk]

This is know limitation of the current implementation:

• order of headers in the AD is ignored
• it's not possible to use same header multiple times, value of the last defined header is used

[netmilk]

I'm sorry, AD = API Description a.k.a API Blueprint document :)