HPE_HEADER_OVERFLOW exception when make http.request

Question

When I tried to get data from REST service, i meet the HPE_HEADER_OVERFLOW error as follow:

var options = {
     host: "something.com",
     port: 80,
     path: "/somepath...",
     method: 'POST'
};

var request = http.request(options, function(res) {
	res.setEncoding('utf8');
	res.on('data', function(chunk) {
		// Do something
	});
	res.on('end', function() {
		// Do something 
	});
	request.on('error', function(e) {
		// Do something
	});
});

request.end();

The length of path parameter in the options is 413.

Does anyone meet this issue? Is this service-side issue or node-side issue?

Please give some idea about it, thanks a lot.

BTW, I tried to make ajax call in browser, it works well.

Steve Gao
– Steve Gao

2016-02-11 00:36:11 +00:00
Commented Feb 11, 2016 at 0:36 — Steve Gao
– Steve Gao, Commented Feb 11, 2016 at 0:36

rahulroy9202 · Accepted Answer · 2019-03-22 10:53:33Z

9

node app.js --max-http-header-size=80000

They made the header size configurable. Check the following links.

https://nodejs.org/api/cli.html#cli_max_http_header_size_size

https://github.com/nodejs/node/issues/24692

answered Mar 22, 2019 at 10:53

rahulroy9202

2,8683 gold badges35 silver badges46 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Martin Lottering Over a year ago

I added the --max-http-header-size=80000 as a runtime argument in the launch.json in Visual Studio Code, and finally got it to work. I used runtimeArgs: [ ... ], not args: [...]

loadaverage · Accepted Answer · 2016-02-11 03:52:35Z

7

I think you'll find more stuff here and here

In a nutshell, Node.js has 80 KB limit for headers size which are big enough for most requests on the web (for example Apache has 8190 bytes limit). If that service somehow has so huge headers you can recompile node with -DHTTP_MAX_HEADER_SIZE=xxxx argument.

answered Feb 11, 2016 at 3:52

loadaverage

1,0561 gold badge11 silver badges16 bronze badges

5 Comments

Steve Gao Over a year ago

Hi man, thanks for your answer, it is very useful for me, but it didn't solve my issue. I just checked the the header size, it didn't exceed the limitation.

loadaverage Over a year ago

Maybe you've run out from system limits or something like this (selinux/apparmor/etc or Node was build with some non-standart options)? I'd like to reproduce this issue if you provide more information (uri and body at least).

Steve Gao Over a year ago

Thanks man for the more suggestions, I just fixed this issue, that's because the REST service always use Content-Encoding: deflate, but when I made the API call, i didn't pass header Accept-Encoding: gzip, deflate. I don't know why the error happen, but the issue has been resolved.

loadaverage Over a year ago

Oh, seems non-properly server stuff. Happy to help somehow.

DShook Over a year ago

Actually only 8kb now :( github.com/Azure/azure-cosmos-js/issues/…

user9373165 · Accepted Answer · 2019-12-13 09:42:29Z

2

After digging a bit, the default parser node uses is the problem. The solution is to get a new parser:

npm install http-parser-js

then, just before you require http/https, change the parser. You have to end up having something similar to this:

process.binding('http_parser').HTTPParser = require('http-parser-js').HTTPParser
const https = require('https')

If for some reason you want to use node's default parser, assuming your file is called 'app.js', you must use the header size flag like this:

node --max-http-header-size=81000 app.js

answered Dec 13, 2019 at 9:42

user9373165

212 bronze badges

Comments

user1002659 · Accepted Answer · 2020-01-14 02:35:11Z

0

I have the same question, but my backend script is PHP. And I return the response header with some internal information including SQL and internal API url, thus the reponse headers is so big that exceeds the max-header-size and encountered this error. You can consider minishing the response header size in some case

answered Jan 14, 2020 at 2:35

user1002659

Comments

Tarun Majumder · Accepted Answer · 2024-05-03 16:59:42Z

0

Use Base64 encoding for the Header data which is causing HPE_HEADER_OVERFLOW like below:

headers: {Cookie: Buffer.from('_oauth2******************************2YJ9Y=').toString('base64')}

answered May 3, 2024 at 16:59

Tarun Majumder

991 silver badge7 bronze badges

Collectives™ on Stack Overflow

HPE_HEADER_OVERFLOW exception when make http.request

5 Answers 5

1 Comment

5 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

1 Comment

5 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related