![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 5 years ago
Closed 5 years ago
#53223 closed defect (bug) (invalid)
REST API: Allow header does not contain DELETE for OPTIONS requests
| Reported by: | talldanwp | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | REST API | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description (last modified by )
Similar to #45753.
A Gutenberg issue (https://github.com/WordPress/gutenberg/issues/31918) flagged that OPTIONS requests don't seem to return DELETE in the allow header.
The presence of PUT might also need to be tested if there are endpoints that support that verb.
To reproduce:
- Login as an admin user
- Open the post editor
- In the console run
wp.data.select( 'core' ).canUser( 'delete', 'posts' ); - Switch to the browser dev tools network tab and check the options request that was just made.
- Observe that the allow header does not contain DELETE, even though the user can delete posts.
Other types of requests to the same endpoint (e.g. GET) return a different allow header with the DELETE verb present.
Change History (3)
Note:
See TracTickets
for help on using tickets.
There is no
DELETEendpoint for/wp/v2/posts, you can only delete a single post. And the delete post capability checks require that post id to be accurate. Making anOPTIONSrequest to for instance/wp/v2/posts/1does include theDELETEmethod in the allow header.