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
{{ message }}
This repository has been archived by the owner on May 22, 2023. It is now read-only.
Under some circumstances, nodejs HTTP Replies are delayed (by about 40ms on Linux) uneededly by Nagle's Algorithm. It would probably be better to solve this upstream, i.e., in the connect server.
The following is a fix, but depends on #94. It can easily be backported though.
// Depending on the request, connect/nodejs write the http header and
// body separately. Set TCP_NODELAY to avoid delays in such situations.
middlewares.push( function( req, res, next ) {
req.socket.setNoDelay( true );
next();
} );
The text was updated successfully, but these errors were encountered:
Under some circumstances,
nodejs
HTTP Replies are delayed (by about 40ms on Linux) uneededly by Nagle's Algorithm. It would probably be better to solve this upstream, i.e., in theconnect
server.The following is a fix, but depends on #94. It can easily be backported though.
The text was updated successfully, but these errors were encountered: