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
llhttp will in certain edge cases (e.g. HEAD, 204, 304) not allow keep-alive to avoid undetectable parsing failures which can lead to data corruption. These can occur when the target server does not properly implement the HTTP/1.1 specification and this is not entirely uncommon.
However, when the target server is known to be spec compliant, this can lead to performance degradation. A typical case for this is when building a microservice architecture where the different services communicate over HTTP/1.1, and the target server is known.
llhttp will in certain edge cases (e.g. HEAD, 204, 304) not allow keep-alive to avoid undetectable parsing failures which can lead to data corruption. These can occur when the target server does not properly implement the HTTP/1.1 specification and this is not entirely uncommon.
However, when the target server is known to be spec compliant, this can lead to performance degradation. A typical case for this is when building a microservice architecture where the different services communicate over HTTP/1.1, and the target server is known.
We recently fixed the case for HEAD requests, but more work can be done here.
The text was updated successfully, but these errors were encountered: