As a result, everything built on top of http-parser implicitly has to support this unstandard header (which can lead to some bugs if you're not expecting this unstandard case to be handled see: https://github.com/envoyproxy/envoy/pull/6749 ),
It'd be great if we had a flag to turn off (or just didn't support at all) this header that isn't part of the standard.
Currently, http-parser will always support the:
Proxy-Connection
header. This header is not standard, and not required for any real legitimate client:are two examples explaining this weird header.
As a result, everything built on top of http-parser implicitly has to support this unstandard header (which can lead to some bugs if you're not expecting this unstandard case to be handled see: https://github.com/envoyproxy/envoy/pull/6749 ),
It'd be great if we had a flag to turn off (or just didn't support at all) this header that isn't part of the standard.