Resolve "HTTP status code for Todos API when an epic cannot be found by a legitimate user is wrongly returning 403 instead of 404"
requested to merge 212817-http-status-code-for-todos-api-when-an-epic-cannot-be-found-by-a-legitimate-user-is-wrong into master
What does this MR do?
This fixes an inconsistency in the Todos API: when an epic cannot be found by a legitimate user is wrongly returning 403 instead of 404.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry - [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team.
Closes #212817 (closed).
Edited by Rémy Coutable