Closed fonsp closed 3 months ago
My goal is to be able to trace the "Server never wrote a response" error to its request. If you prefer, I can also add this information to https://github.com/JuliaWeb/HTTP.jl/blob/eb1d2a9dfcec489eac17f4f34190df45b7873d66/src/Servers.jl#L472 and leave the logging for other handler errors as-is.
Attention: Patch coverage is 0%
with 1 lines
in your changes are missing coverage. Please review.
Project coverage is 83.19%. Comparing base (
eb1d2a9
) to head (28ed65b
).
Files | Patch % | Lines |
---|---|---|
src/Servers.jl | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This will show the request that caused a handler error in the log.
For example, if I add
error("Test")
in my handler, I get this log:Instead of this:
I think this is useful debugging information! For example, I am currently trying to chase down the origin of a "Server never wrote a response" (like #1023 and #1156). Since my app is quite complex, it's really useful to know the path and method of the request that was handled wrong.