-
-
Notifications
You must be signed in to change notification settings - Fork 172
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.
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
Should INTERNAL_SERVER_ERROR be UNAUTHENTICATED/FORBIDDEN? #1176
Comments
Hey @reergymerej 👋, Thank you for opening an issue. We will get back to you as soon as we can. Have you seen our Open Collective page? Please consider contributing financially to our project. This will help us involve more contributors and get to issues like yours faster. https://opencollective.com/graphql-shield
|
Extra Info In It still seems like the basic "Not Authorised!" response should use |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Question about GraphQL Shield
Unauthenticated requests are blocked, but the error code returned by Apollo is always
INTERNAL_SERVER_ERROR
. Is this expected? Is there a a configuration I'm missing somewhere?Question about GraphQL concepts
I expect Apollo responses with auth errors to have HTTP code 200 and a body with an error
extension.code
UNAUTHENTICATED
.https://www.apollographql.com/docs/apollo-server/data/errors/#unauthenticated
#120 - looks promising, but way old (using 7.3.2 now)
#767
The text was updated successfully, but these errors were encountered: