Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Jetty9: unhandled response should be counted as 404 and not 200 #1232
In Jetty, a request that has not been handled by the handler chain keeps the default status code 200, and a 404 response is produced by
To reveal the issue, this PR removes the 404 response from
This PR is against branch
Thanks for spotting this bug! I agree that an unhandled request should be counted as an error (because there's no handler that handles the request).
I'm still maintaining the 3.2 branch, so the fix is good enough to merge to it. I will also cherry-pick it to the 4.0 branch.