等等，第一个没有被 deprecate 啊

第二个，你看了 RFC 没？ www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2

其中关键的部分：

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)]. It MUST be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics of the message, by appending each subsequent field-value to the first, each separated by a comma. The order in which header fields with the same field-name are received is therefore significant to the interpretation of the combined field value, and thus a proxy MUST NOT change the order of these field values when a message is forwarded.

@yegle 我信你个鬼 rfc 这个地方坏的很😂。。。代码没有写完，就不在 Android 里面测试了，不过猜测 99.99% Google 的那个临时工更加不会去对响应头 value 内的格式进行深度处理。

`by appending each subsequent field-value to the first, each separated by a comma`，浏览器里面跑一边看看能否识别用逗号拼接的：




另外搞笑的是 URLConnection 获得的响应头是 Map<String,List<String>>结构，chorme 也是谷歌自家的玩意，综合起来可笑不可笑

头部数据还是是对象？楼主怕是在做 http 5G 的梦吧

@xuanbg 有哪个语言的 http 库头部数据不是对象的吗？
1. 这语言根本没人用
2. 这语言没有对象只有字符串
3. 第二天就有人写个封装

@xuanbg 哈哈，数组也是可以的，只要能把数据完整的表达😏
1. ["k1: v1", "k2: v2"]
2. ["k1","v1", "k2","v2"]
3. "k1: v1 \n k2: v2" 没区别😂
4. 5G 锟斤拷烫烫烫

这个坑估计迟早要亲自踩，先 mark 一下......
话说往 header 里面塞乱七八糟东西还各有各的格式这股风气怎么刮起来的...是 RESTful 还是 ws 干的，接触少还不知道影响有多大。