Inexistent 403 responses in a plone.restapi GET call to content
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 109
- Forks
- 107
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 4
Description
While authenticated, you ask for a content that the user do not have permissions, Zope answers Unauthorized, instead of a Forbidden.
I don't know if that's a regression for Plone 5.2, since it's using the WSGI stack.
It has more to do with p.rest than p.restapi, I will open this one to have the issue in sight.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the authenticated GET request described in plone.restapi, then compare the permission response through p.rest and the WSGI stack. Confirm the expected behavior for content the user cannot access: the request should return Forbidden (403) rather than Unauthorized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100