-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scanner returns HPE_HEADER_OVERFLOW at startup #64
Comments
Not sure if lando's built-in Node respects the environment variable, but does this work? NODE_OPTIONS='--max-http-header-size=32000' lando start |
No, that didn't work. I think that environment variable (or command line argument) needs to be set internally in Lando's scanner environment, but I don't know how to do that. |
FACING THE SAME issue! |
FYI I was able to work around this issue by configuring the URL scanner to check a different URL than my homepage. I pointed it to my login URL which has fewer HTTP headers since it's not cached. .lando.yml
|
Ah, that is interesting, going to move this over to the |
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?
The text was updated successfully, but these errors were encountered: