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
I've not dug in to why morgan fails in this case, but when a cache-hit is successful it is unable to register response times or content content length. This seems to be due to morgan relying on the lifetime events fired by response.send/end. Note that firing res.end() after socket.end() does fix the response time but leaves content-length empty (headers are of course correct but morgan results are not)
The text was updated successfully, but these errors were encountered:
I've not dug in to why morgan fails in this case, but when a cache-hit is successful it is unable to register response times or content content length. This seems to be due to morgan relying on the lifetime events fired by response.send/end. Note that firing res.end() after socket.end() does fix the response time but leaves content-length empty (headers are of course correct but morgan results are not)
The text was updated successfully, but these errors were encountered: