WordPress.org
Get WordPress

Making WordPress.org

Changes between Initial Version and Version 1 of Ticket #6221


Ignore:
Timestamp:
03/28/2022 05:05:57 AM (4 years ago)
Author:
dd32
Comment:

401/403 are permission-related statuses, which do not make sense to be used in this context IMHO.

Updated to reflect 410 Gone rather than 401.

​https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410

The HyperText Transfer Protocol (HTTP) 410 Gone client error response code indicates that access to the target resource is no longer available at the origin server and that this condition is likely to be permanent.

There's three statuses we can use here:

  • 200 (Current)
  • 404 (Temporarily not here)
  • 410 (Permanently gone, no longer exists).

When a plugin is closed, we currently return a robots noindex tag for closed plugins but keep 200 as the status code.

I don't think we should return 404 for plugins that exist, but are no longer available.

410 Makes the most sense to me.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6221

    • Property Summary changed from Use `401 Gone` response on permanently closed plugin pages. to Use `410 Gone` response on permanently closed plugin pages.

  • Ticket #6221 – Description

    initial v1  
    1 Plugin pages for permanently closed plugins currently emit a HTTP `200 OK` response. For these pages a `401 Gone` response makes more sense.
     1Plugin pages for permanently closed plugins currently emit a HTTP `200 OK` response. For these pages a `410 Gone` response makes more sense.
    22
    33I suggest this for both developer initiated (such as [https://wordpress.org/plugins/rapid-adn-widget/ this plugin for app.net]) and plugin team initiated closures.