blocks|key|811634|text|解决方案是这个库：https://www.npmjs.com/package/http-parser-js|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|811635|所以要解决你的问题：|811636|npm安装http-解析器-js|ordered-list-item|811637|在请求之前添加此代码(“请求”)
process.binding('http_parser').HTTPParser+=需要量(‘http-解析器-js’).HTTPParser；|811638|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/http-parser-js^0|9|18|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$]]|$1|I|3|J|5|H|7|Y|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

The solution is this library: <a href="https://www.npmjs.com/package/http-parser-js" rel="noreferrer">https://www.npmjs.com/package/http-parser-js</a>

So to fix your problem:

<ol>
<li>npm install http-parser-js</li>
<li>Add this code before require('request')

<pre><code>process.binding('http_parser').HTTPParser = require('http-parser-js').HTTPParser;
</code></pre></li>
</ol>

blocks|key|811661|text|Node+v12有一个新的解析器，它对头验证更加严格，这可能导致同样的错误，特别是对于使用Imperva/In蒴a在HTTP1.1响应中包含无效报头的站点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|811662|临时解决方案是在节点的命令行或NODE_OPTIONS环境变量中使用NODE_OPTIONS选项。|offset|length|style|CODE|811663|由于v12.15.0和v10.19.0，您可以这样做：|811664|http.request(url,+{+insecureHTTPParser:+true+})|code-block|syntax|javascript|811665|更多信息可以在这里找到：https://github.com/nodejs/node/issues/27711#issuecomment-584621376|811666|编辑：在最近的版本中不再支持--http-parser=legacy+(包括v12的次要版本)。更新节点版本的解决方案是使用--insecure-http-parser代替。|BOLD|811667|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nodejs/node/issues/27711#issuecomment-584621376^0|0|F|C|Y|C|0|2|8|B|8|0|0|C|1U|0|0|0|2|E|K|1Q|M|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@$D|13|E|14|F|G]|$D|15|E|16|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|17|8|@$D|18|E|19|F|G]|$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|1C|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|Q|3|R|5|6|7|1H|8|@$D|1I|E|1J|F|S]|$D|1K|E|1L|F|G]|$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

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 <code>--http-parser=legacy</code> option in node's command line, or in the <code>NODE_OPTIONS</code> environment variable.

Since <code>v12.15.0</code> and <code>v10.19.0</code> you can do this:

<pre><code>http.request(url, { insecureHTTPParser: true })
</code></pre>

Additional information can be found here:
<a href="https://github.com/nodejs/node/issues/27711#issuecomment-584621376" rel="noreferrer">https://github.com/nodejs/node/issues/27711#issuecomment-584621376</a>

Edit: <code>--http-parser=legacy</code> is no longer supported in recent versions (including minor versions of v12). A solution for newer node versions is to use <code>--insecure-http-parser</code> instead.

blocks|key|2019271|text|我也有同样的问题，像这样运行代码对我来说是有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2019272|nodemon+--http-parser=legacy|offset|length|style|CODE|2019273|entityMap^0|0|0|S|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had the same issue, running the code like this worked for me
<code>nodemon --http-parser=legacy</code>

blocks|key|2019306|text|具有相同的错误，并且提供的解决方案不再在节点v14和v16中工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2019307|我最后使用了node-libcurl+(节点v16.15.1)|offset|length|style|CODE|2019308|const+{+Curl+}+=+require('node-libcurl');

const+curl+=+new+Curl();

var+api_URL+=+"https://www.......";

curl.setOpt('URL',+api_URL);
curl.setOpt('FOLLOWLOCATION',+true);
curl.setOpt(Curl.option.HTTPHEADER,+['Content-Type:+application/json',+'Authorization:+Bearer+XYZ']);

curl.on('end',+function(statusCode,+data,+headers)+{

++++//+do+something+with+the+data+you+get..
++++//+.....

++++this.close();

});

curl.on('error',+curl.close.bind(curl));
curl.perform();|code-block|syntax|javascript|2019309|如果您希望查看标题的外观，请添加以下选项：|2019310|+++curl.setOpt(Curl.option.VERBOSE,+true);|2019311|entityMap^0|0|6|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Had the same error and provided solutions are not working anymore in node v14 and v16.
I ended up using <code>node-libcurl</code> (with node v16.15.1)
<pre><code>const { Curl } = require('node-libcurl');

const curl = new Curl();

var api_URL = &quot;https://www.......&quot;;

curl.setOpt('URL', api_URL);
curl.setOpt('FOLLOWLOCATION', true);
curl.setOpt(Curl.option.HTTPHEADER, ['Content-Type: application/json', 'Authorization: Bearer XYZ']);

curl.on('end', function(statusCode, data, headers) {

 // do something with the data you get..
 // .....

 this.close();

});

curl.on('error', curl.close.bind(curl));
curl.perform();
</code></pre>
If you like to see how your Header looks like, add this option:
<pre><code> curl.setOpt(Curl.option.VERBOSE, true);
</code></pre>

blocks|key|811765|text|通过在原始模式下检查Chrome+Tools中的标头，我能够找到问题所在(是哪个标头导致了这个问题)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|811766|​|811767|📷|atomic|offset|length|811768|811769|原来我有“内容-类型：”没有类型。|811770|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/cd5ba477f2236c9f518aa8ea50ea566b.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

I was able to find what was the problem (which header was causing this) by inspecting headers in the Chrome Dev-Tools in RAW mode.
<a href="https://i.stack.imgur.com/Qhyya.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Qhyya.png" alt="chrome dev tools screenshot" /></a>
Turns out I had &quot;Content-Type:&quot; without a type.

I receive <code>HPE_INVALID_HEADER_TOKEN</code> on a certain page using <code>request</code> 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?

Nodejs request: HPE_INVALID_HEADER_TOKEN

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我使用HPE_INVALID_HEADER_TOKEN模块在特定页面上接收request。据我在Google上所发现的，这是由一个不正确/格式错误的服务器响应引起的，而后者并不在我的控制范围之内。我是否可以将请求配置为忽略无效的标头，或者只为处理提供整个原始响应？

问Nodejs请求: HPE_INVALID_HEADER_TOKEN
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nodejs请求: HPE_INVALID_HEADER_TOKENEN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nodejs请求: HPE_INVALID_HEADER_TOKEN
EN