[wp-gsoc] [Summer of Code] #338: HTTP Status 405 on disabled should be 403

Summer of Code noreply at wordpress.org
Wed Jul 24 04:43:00 UTC 2013

#338: HTTP Status 405 on disabled should be 403
 Reporter:  MikeSchinkel   |       Owner:
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:
Component:  JSON REST API  |  Resolution:
 Keywords:                 |

Comment (by MikeSchinkel):

 HTTP status codes are meant as responses to the user agent, not as
 responses for the user. It's the user agent's responsibility to translate
 to into user-friendly terms.  Thus 404 is not appropriate here because the
 resource ''was'' indeed found, it was just not accepting responses; the
 latter is what 403 was intended for.

 410 might have been appropriate if it were not for the fact that it
 includes the language ''"Indicates that the resource requested ... will
 not be available again."''  Given that it is likely many users will enable
 disabled APIs after they realize they need them sending a 410 could result
 in [http://datatracker.ietf.org/wg/webi/charter/ web intermediaries]
 refusing to send new requests if they have already cached a 410 response.

Ticket URL: <https://gsoc.trac.wordpress.org/ticket/338#comment:2>
Summer of Code <https://gsoc.trac.wordpress.org>
My example project

More information about the wp-gsoc mailing list