Skip to content
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.

Sign up for GitHub

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

Jump to bottom

200 status is incorrectly logged when connection is aborted #58

Open
jonmellman opened this issue Jan 21, 2021 · 0 comments
Open

200 status is incorrectly logged when connection is aborted #58

jonmellman opened this issue Jan 21, 2021 · 0 comments

Comments

@jonmellman
Copy link

express-bunyan-logger incorrectly logs a 200 response code when connections are aborted. This happens when a connection is closed due to timeout (server.timeout value is reached), for example.

Other libraries correctly report undefined instead of 200 in this case. For example, see this morgan issue and the corresponding source code here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonmellman