> We are currently developing a new REST API for our proprietary CMS and > it will have support for HEAD requests, this is, as you mentioned, the > server wont process the full request as if it was a GET but return a > different response instead.
Hmm, but it shouldn't return a different response. The "spirit" of HEAD (it is an RFC SHOULD) is that it is identical to a GET for the same entity, except that only the headers are returned. That's why it's more of a convenience method that's most useful when you don't control the server and you want to make sure that it doesn't put extra bytes on the wire. If you do control the server (as with your proprietary platform) there's no advantage over sending a custom request for /EN/TI/TY/HEAD /EN/TI/TY/FULL etc. I agree that it would be nice if Moo supported it (although every XHR object doesn't -- I think this would break IE 6 BC), but it shouldn't be a stopping point for your project, since you can wrap the same functionality in the request parameters. -- S.
