Re:Golang's network stack attempts to parse HTTP headers as ...
by _wldu on Thursday January 21, 2021 @09:44AM
(#25859312)
There's a reply in that Twitter Thread. Go will be switching to ASCII: "Thanks for the ping. Our policy is that anything that requires a proxy to forward an invalid Transfer-Encoding header is a vulnerability in the proxy, not in the server. We are planning to switch all net/http to ASCII strings functions anyway for defense in depth and correctness." - Filippo Valsorda, Go Security Lead
[ Parent
| on HN ]
Re:Golang's network stack attempts to parse HTTP headers as ...
by lucideer on Thursday January 21, 2021 @09:49AM
(#25859349)
> Our policy is that anything that requires a proxy to forward an invalid Transfer-Encoding header is a vulnerability in the proxy
It's great that they're fixing this anyway, but that's a bad policy.
Re:Golang's network stack attempts to parse HTTP headers as ...
by jeff-davis on Thursday January 21, 2021 @11:46AM
(#25860896)
That was my initial reaction as well, but I'd like to hear some more explanation.