The logical distinction is transport headers vs content headers. I think
the network owner and peers should decide issues related to transport
(Connection headers, cache headers, transfer headers, delimiter related
headers, etc..) but someone closer to Firefox / Thunderbird / etc should
set those for U-A, Content, etc.. (perhaps differently from other products).
On 2/26/2012 9:57 PM, Brian Smith wrote:
I don't think "HTTP Headers" is a good module to have. Content team (for Accept-*) or
Necko team (everything else except User-Agent) is the one that should "own" most of the
other headers, and to make it simple, we might as well keep them in Necko. User-Agent is the only
header that Necko team would say good riddance to, AFAICT.
Cheers,
Brian
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
