question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Parse Error: header overflow [errored]

See original GitHub issue

image

When I’m running my collection against Identity Server using POSTMAN they are running smooth and perfect but after exporting and running from NEWMAN I’m getting this error visible on the screen.

**Parse Error: header overflow [errored]**

The request causing error is POST request with application/x-www-form-urlencoded and in form data I have state and id_token (first 859 char, second 1644 char). The NEWMAN fails on making the request itself (I think). I know it cause the server works against the browser, against POSTMAN and the request works in NEWMAN when I put shorter, fixed strings of data (but obviously server gives response about unauthorized call)

Anybody has any idea how it may be solved or how to find out if it’s a bug? In the source code I didn’t see much about logger.

I tried:

  • Running via API, via Powershell, via POSTMAN API
  • Tried putting fixed strings into those variables (same variables but put manually cause this error, shorter work)
  • Increasing header size
  • Cleaning cookies before runs

It seems like NEWMAN fails to make the request because of the size of the header? Or maybe it’s something with encoding/exporting to collection? Any ideas? If so, maybe clues on how can I fix it?

Newman Version 4.5.7 OS details Win10 Are you using Newman as a library, or via the CLI: Tried both
Did you encounter this recently, or has this bug always been there: No info about the bug anywhere. Expected behaviour: It should make a request at least. Looks like it fails before sending it Command / script used to run Newman: newman run .\NEWMAN.postman_collection.json --ignore-redirects

I can’t provide the collection as it’s data that can’t be compromised. Tried to be specific as per what am I passing to the request.

Issue that may be similar / relevant

#2182 #1224

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:1
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

3reactions
Sviatoycommented, Jun 9, 2020

@hvitis Node v.10.12.0 - it’s a workaround.

SOLUTION: node --max-http-header-size=40960 It should work for latest node

2reactions
hvitiscommented, Jan 20, 2020

@coditva You have saved my life.

SOLUTION: Works with Node v.10.12.0 // npm v6.4.1 // newman v4.5.7

Read more comments on GitHub >

github_iconTop Results From Across the Web

"Parse Error: Header overflow" During Node.js GET Request
I am trying to submit a form through Google forms programmatically through a GET request, but I am receiving the error Parse Error:...
Read more >
NEWMAN-only Parse Error: header overflow [errored] - Help
When I'm running my collection against Identity Server using POSTMAN they are running smooth and perfect but after exporting and running from ...
Read more >
WORKFLOW STOPPED: Parse Error: Header Overflow - Help
I made tests on different platforms postman, integromat, etc - everything works as it should, and no errors are received. Sometimes It goes...
Read more >
Changelog - Cypress Documentation
Fixed a regression in 3.5.0 where certain HTTP requests could fail with Parse Error: Invalid header value char or Parse Error: Header overflow...
Read more >
postman parse error: expected http
The error manifests itself with Postman as 'Error: Parse Error: Header overflow'. Deeper inspection using curl shows that there is an element in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found