Scanner returns HPE_HEADER_OVERFLOW at startup
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 41
- Avg merge
- 2h 1m
- Merged PRs (30d)
- 2
Description
Recently when running lando start the scanner for one of our websites started returning red URLs with HPE_HEADER_OVERFLOW errors, despite the fact that the URLs all load just fine in the browser.
It appears this error is related to exceeding a max header size of 16 KB in Node.js.
Sure enough, I looked and our site had 17 KB of headers due to somewhat lengthy content-security-policy, surrogate-key, and x-drupal-cache-tags headers. I tried turning off the CSP header which reduced the size to about 16 KB and now the URLs are green again when I restart Lando.
Is there any way to adjust the max header size allowed by the scanner?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the scanner path invoked by lando start and review Node.js --max-http-header-size behavior. Determine how the scanner's header limit is configured, then verify that URLs with headers above 16 KB no longer produce HPE_HEADER_OVERFLOW errors while scanning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100