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

[Summer of Code]

#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):

 Replying to [comment:3 bpetty]:
 > Except that a 403 also indicates that, should the browser provide
 appropriate authentication credentials, it *would* be successful, but
 that's not true either. Reserving 403 strictly for auth credential issues
 (as that's what it will mostly be used for)...

 As I
 [http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_Client_Error
 read Wikipedia], it reads to me that you've got it wrong. This is what is
 says about 403, ''('''emphasis mine'''):''

 > ''The request was a valid request, but the server is refusing to respond
 to it.[2] '''Unlike a 401 Unauthorized response, authenticating will make
 no difference.'''[2] On servers where authentication is required, this
 commonly means that the provided credentials were successfully
 authenticated but that the credentials still do not grant the client
 permission to access the resource (e.g. a recognized user attempting to
 access restricted content).''

 So it would seem you are referring to a 401, not a 403?

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