[wp-hackers] HTTP Request API edge case

Mike Schinkel mikeschinkel at newclarity.net
Sun Jul 19 19:21:55 UTC 2009

"Heiko Rabe" <heiko.rabe at code-styling.de> wrote:
> excluding PUT would not a good idea


DELETE is also needed. Without it you can't create a RESTful web service [1][2][3].

"Jacob Santos" <wordpress at santosj.name> wrote:
> or one of the HTTP 1.1,

Or did we misunderstand?  By saying HTTP 1.1 were you implying PUT and DELETE?  If so, forgive the intrusion.

-Mike Schinkel
Custom Wordpress Plugins

[1] http://www.artima.com/lejava/articles/why_put_and_delete.html
[2] http://www.xml.com/pub/a/2004/12/01/restful-web.html
[3] http://en.wikipedia.org/wiki/Representational_State_Transfer#RESTful_example:_the_World_Wide_Web

----- Original Message -----
From: "Heiko Rabe" <heiko.rabe at code-styling.de>
To: wp-hackers at lists.automattic.com
Sent: Sunday, July 19, 2009 3:13:03 PM GMT -05:00 US/Canada Eastern
Subject: Re: [wp-hackers] HTTP Request API edge case

I think, that excluding PUT would not a good idea, because the cloud 
computing from Microsoft's Azure Platform 
http://www.microsoft.com/azure/default.mspx needs as example for azure 
blobs a PUT.
Most of this services can be used RESTful and HTTP/HTTPS based, so this 
may also be a future option to integrate useful services into WP out of 
the clouds.


> No, there aren't any methods that currently exist that are mixed case or lower case. All existing methods are uppercase. That is not to say that there couldn't be or won't be in the future. It is also to say that most of the time, we should be doing POST, GET, or HEAD. All of the others such as PUT, have no guarantee to be supported on the server we are requesting, and most likely would be blocked from doing a PUT request.
> Furthermore, if someone is using a non-standard method, they either know what they are doing, or should not be doing it. Alas, such things should probably be in a header than a method as the server probably won't know what to do with it otherwise. There is a reason DAV requires an extension, is that it is an extension to the HTTP 1.1 standard and not part of it.
> So in conclusion, if someone is doing something other than POST, GET, HEAD, or one of the HTTP 1.1, then they are doing it wrong and therefore we can safely uppercase the method.

wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list