- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Servers - General
- >
- Nodejs request: HPE_INVALID_HEADER_TOKEN
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2021 02:14 AM - edited 11-08-2021 01:03 AM
11-03-2021 02:14 AM - edited 11-08-2021 01:03 AM
Nodejs request: HPE_INVALID_HEADER_TOKEN
I get HPE_INVALID_HEADER_TOKEN on a specific page utilizing demand module. From what I've found on Google, this is brought about by a wrong/deformed server reaction, but the last option isn't influenced quite a bit by. Would i be able to design demand to overlook invalid headers or simply give me the entire crude reaction for handling?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2021 08:20 AM
11-03-2021 08:20 AM
Re: Nodejs request: HPE_INVALID_HEADER_TOKEN
Hi,
The error HPE_INVALID_HEADER_TOKEN, as far as I know, its not related to HPE domain or company.
https://github.com/node-red/node-red/issues/974
http://www.yeolar.com/media/doc/coral/html/http__parser_8h.html
Thanks
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2022 03:13 AM
03-08-2022 03:13 AM
Re: Nodejs request: HPE_INVALID_HEADER_TOKEN
Node v12 has a new parser that is more strict with header validation, which can cause the same errors, especially with sites using Imperva/Incapsula that include an invalid header in HTTP 1.1 responses.
A temporary solution is to use the --http-parser=legacy option in node's command line, or in the NODE_OPTIONS environment variable.
Since v12.15.0 and v10.19.0 you can do this:
http.request(url, { insecureHTTPParser: true })
Additional information can be found here: https://github.com/nodejs/node/issues/27711#issuecomment-584621376
Edit: --http-parser=legacy is no longer supported in recent versions (including minor versions of v12). A solution for newer node versions is to use --insecure-http-parser instead. Crediblebh