News for hackers. Stuff that matters.

A comment on Go: What We Got Right, What We Got Wrong. Parent comment

Re:Go: What We Got Right, What We Got Wrong by akoboldfrying on Thursday January 04, 2024 @11:45PM (#38875772)
No, and that wasn't the claim being made. The claim being made was that there can be engineering value in preserving the case of existing headers.

Example: An HTTP proxy that preserves the case of HTTP headers is going to cause less breakage than one that changes them. In a perfect world, it would make no difference, but that isn't the world we live in.

[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by aatd86 on Friday January 05, 2024 @04:18AM (#38877197)
Are you sure they are discarded and unrecoverable? Can't that be simply recovered by using textproto.MIMEHeader and iterating over the header map?

Seems that it could be a middleware away, I don't see the big deal if so.

[ Parent | on HN ]
Re:Go: What We Got Right, What We Got Wrong by akoboldfrying on Saturday January 06, 2024 @09:50PM (#38897956)
You may well be right -- I don't know Go at all, and just assumed the parent post's claim is true.
[ Parent | on HN ]