Doc Feedback: 404 is thrown instead of 403 when a request is sent with an unmatching resource
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
The documentation mentions that APIM sends a 403 Forbidden error code when a request is sent with an unmatching resource. But actually, the APIM returns a 404 not found error code. This should be fixed.
404 codes are set to the context in following places of the code:
Location : https://apim.docs.wso2.com/en/latest/troubleshooting/error-handling/
Contributor guide
No contributing guide indexed for this repository
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
Open the troubleshooting/error-handling documentation page linked in the issue and locate the statement that APIM returns 403 for an unmatching resource. Compare it with the 404 status references in CORSRequestHandler.java at lines 188 and 274. Update the documented status to match the observed behavior, then check the rendered page for consistent wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100