Opened 15 years ago
Closed 11 years ago
#11113 closed enhancement (wontfix)
Return 410 Gone HTTP response for deleted posts/pages
Reported by: | voyagerfan5761 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.9 |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
Deleted content should be treated differently from content that never existed. WordPress could be enhanced by returning a 410 Gone response to requests for posts or pages that have been deleted.
As I currently envision the solution, bits of old content (like a slug) would have to remain in the database after deletion.
Using WordPress 2.8.5; could not find any references to this in pre-existing Trac tickets in Core.
Change History (4)
#1
follow-up:
↓ 3
@
15 years ago
- Milestone changed from Unassigned to Future Release
- Version changed from 2.8.5 to 2.9
Note: See
TracTickets for help on using
tickets.
I don't think it's worth storing old data in the DB just for this.
At most, 410 could be sent for posts and comments that are currently in the trash.