Adding nodejs http.request option: insecureHTTPParser for interoperability

[fabiel-leon]

February 2020 Security Releases
by Sam Roberts, 2020-02-06 Nodejs has increase the strictness of HTTP header parsing. There are no known vulnerabilities addressed, but lax HTTP parsing has historically been a source of problems. Some commonly used sites are known to generate invalid HTTP headers, a --insecure-http-parser CLI option or insecureHTTPParser http option can be used if necessary for interoperability, but is not recommended.
https://nodejs.org/en/blog/vulnerability/february-2020-security-releases/#strict-http-header-parsing-none

Bug Error: Parse Error: Invalid header value char

adding the new option for nodejs http.request: insecureHTTPParser for interoperability

see nodejs http.request options docs

see nodejs/node#27711

[chinesedfan]

Added to #2808.

[github-actions]

Hello! 👋 \n\nThis pull request is being automatically marked as stale because it has not been updated in a while. Please confirm that the issue is still present and reproducible. If no updates or new comments are received the pull request will be closed in a few days. \n\nThanks

[queso]

It seems the new boolean value was missed in the request config type interface