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
What are you trying to achieve or the steps to reproduce?
I have a hapi server with a route that performs a potentially long-running calculation before responding. Sometimes clients timeout or abort their request before the server has responded. When this occurs, the server logs the response status code as 200 rather than 499. I don't believe this is an issue with the logger, because both good/good-console and hapi-pino have the same behavior.
Server running at: http://localhost:8080
Event: {"request":"<SHORTENED>","timestamp":1584125752386,"tags":["request","error","abort"],"channel":"internal"}
Response Status Code: 200
Support plan
Context
What are you trying to achieve or the steps to reproduce?
I have a hapi server with a route that performs a potentially long-running calculation before responding. Sometimes clients timeout or abort their request before the server has responded. When this occurs, the server logs the response status code as 200 rather than 499. I don't believe this is an issue with the logger, because both good/good-console and hapi-pino have the same behavior.
What was the result you got?
Server running at: http://localhost:8080 Event: {"request":"<SHORTENED>","timestamp":1584125752386,"tags":["request","error","abort"],"channel":"internal"} Response Status Code: 200What result did you expect?
Response status code to be 499 (not 200).