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

Derby should not show a stack trace when GET on a resource that doesn't exist. #15

Open

jcoyne opened this issue Jun 12, 2017 · 1 comment

jcoyne commented Jun 12, 2017

Returning a 404 status should be sufficient.

Member

no-reply commented Nov 11, 2017

Are there steps to repeat?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment