REST API: Fix incorrect 403 status code for invalid post ID in Comments controller.#11529
Open
saratheonline wants to merge 1 commit intoWordPress:trunkfrom
Open
REST API: Fix incorrect 403 status code for invalid post ID in Comments controller.#11529saratheonline wants to merge 1 commit intoWordPress:trunkfrom
saratheonline wants to merge 1 commit intoWordPress:trunkfrom
Conversation
…ts controller. `update_item()` was returning HTTP 403 (Forbidden) when a non-existent post ID was provided. The correct status is 404 (Not Found), as the resource is missing — not access-restricted. This also makes `update_item()` consistent with `get_item()` in the same controller, which already returns 404 for the same scenario.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
update_item()was returning HTTP 403 (Forbidden) when a non-existentpost ID was provided. The correct status is 404 (Not Found), as the
resource is missing — not access-restricted.
This also makes
update_item()consistent withget_item()in thesame controller, which already returns 404 for the same scenario.
Trac ticket: https://core.trac.wordpress.org/ticket/65050
Fixes: #65050
Use of AI Tools
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.