It seems that all communication is now expected to work through the GET and POST methods. The GET is intended for retrieving data with potential for cache. The POST is intended to push data onto the server. These two methods are very common and do not require a lot of discussion.
The OPTIONS method intends to determine what options are available to the client. This may be useful in the cases of determining a user has access to specific resources on the server. The w3.org HTTP v1.1 specification has this to say about OPTIONS.
The OPTIONS method represents a request for information about the communication options available on the request/response chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
Responses to this method are not cacheable.In the Book example I have been working through, I could it being used to determine if a user has read-only access or may have create, update and delete privileges as well. The client application could be formed in a way to respect the response of an OPTIONS request to provide certain features to the user based on their authorizations.
HEAD, is header that I have only read about and never use in practice. The definition as defined by w3.org from the HTTP v1.1 specification is,
The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext links for validity, accessibility, and recent modification.Two things come to mind. Checking the end point is valid and exists, pushing data to the server without sending a response to the client. Now these two are likely very useful in certain conditions.
My extinct is to avoid HEAD whenever the User's experience is at stake. Another words, if there is a need to make a request to the server to gather information. It does not seem practical or feasible to make a HEAD request first to determine if the end point is valid and contains fresher data than the browser's cache. The result would be in certain situations an additional request to retrieve the data.
I can see this being used in a CDN type implementation, where the delivery nodes are responsible for checking for updates periodically. In this instance that User is waiting for the response and additional requests. The node can make requests more often to check staleness using HEAD and then make a GET request to retrieve an update when necessary.
Another useful condition may be to push user activity information to the server. In this case, the response codes should indicate whether the user is still allowed to access the system. Otherwise, if the system is dependent on the client pushing data or communicating on a regular basis to avoid a session disruption from the server side.
PUT and DELETE Methods
The PUT and DELETE methods are primarily used in RESTful services. They are used to indicate the action of updating or deleting some data. I have already worked through the PUT and DELETE methods in a previous post. Check it out for what I have discovered there
TRACE is a method intended for testing and debugging purposes. The method indicates that the server should do nothing more than reflect the request data back to the client. HTTP v1.1 identifies this as,
The TRACE method is used to invoke a remote, application-layer loop- back of the request message. The final recipient of the request SHOULD reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see section 14.31). A TRACE request MUST NOT include an entity.
This is useful to identify how a request may be processed on the way through all of the various hops between the client application and the server. If there are no hops between the client and server there is likely going to very little change of the request on the way through to the server. I have never used this in practice, but I am intrigued to learn more about it and how I may be able to utilize it.
This method appears to be reserved but not implemented. So there is not much to say about it, except it may be used with SSL tunneling. See the w3.org's HTTP v1.1 specification for more details and updates to the specification.