topic Re: HPE_INVALID_HEADER_TOKEN : Nodejs request in Servers - General

HPE_INVALID_HEADER_TOKEN : Nodejs request

Joseph735 — Fri, 22 Apr 2022 12:47:14 GMT

I receive HPE_INVALID_HEADER_TOKEN on a certain page using request module. From what I've found on Google, this is caused by an incorrect / malformed server response, however the latter is not under my control. Can I configure request to ignore invalid headers or just give me the whole raw response for processing?

Re: HPE_INVALID_HEADER_TOKEN : Nodejs request

Parvez_Admin — Mon, 11 Nov 2019 08:01:23 GMT

Hi Joseph,

Can you please provide more details about which HPE product this is related to so that we can direct your question to the correct discussion board.

Re: HPE_INVALID_HEADER_TOKEN : Nodejs request

Al22ma — Thu, 06 Feb 2020 09:45:34 GMT

I receive HPE_INVALID_HEADER_TOKEN on a certain page using request module.

Re: HPE_INVALID_HEADER_TOKEN : Nodejs request

Spencer235 — Fri, 04 Jun 2021 07:17:28 GMT

Thank you for information

Re: HPE_INVALID_HEADER_TOKEN : Nodejs request

Aimee21 — Wed, 02 Feb 2022 04:05:40 GMT

Node v12 has a new parser that is more strict with header validation, which can cause the same errors, especially with sites using

Re: HPE_INVALID_HEADER_TOKEN : Nodejs request

rnestina — Sat, 12 Mar 2022 09:30:03 GMT

It does look like the new parser of Node 12 is more strict. However, since the error comes from a remote server that is entirely beyond our control, it seems that a more strict parser is a disadvantage, rather than an advantage.

Do you know whether the legacy option will ever be removed in the future? I worry that it will cause a lot of problems that can't be fixed from our end