You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently limit to 16 headers, which is insufficient for expected demands, particularly with increased numbers of "Sec-*" headers being provided by nightly.
Note: this will return a Severity: 7 error "Fields":{"msg":"127.0.0.1:46460: too many headers"}. I suspect this is not being logged. We may wish to increase visibility of this error in the future.
The text was updated successfully, but these errors were encountered:
Can we tell cargo audit to ignore it somehow, and get this fixed before updating hyper? I'll get our hyper updated asap, but we shouldn't block this bug on it.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1623400
We currently limit to 16 headers, which is insufficient for expected demands, particularly with increased numbers of "Sec-*" headers being provided by nightly.
Current header list may include:
Note: this will return a Severity: 7 error
"Fields":{"msg":"127.0.0.1:46460: too many headers"}
. I suspect this is not being logged. We may wish to increase visibility of this error in the future.The text was updated successfully, but these errors were encountered: