Common HTTP Methods & Description

HTTP Methods & Description
OPTIONS : Used by client applications to request a list of all supported verbs. In this way, you can check to see if a server allows a particular verb before wast-ing network bandwidth trying to send an unsupported request.
GET : Gets a URL from the server. A GET request for a specific URL, say, Shaneesh.htm, retrieves the shaneesh.htm file. Data retrieved using this verb is typically cached by the browser. GET also works with collections, such as those in directories that contain collections of files. If you request a directory, the server can be configured to return a default file, such as index.html, that may be representative of the directory.
HEAD : Retrieves the meta information for a resource. This information is typically identical to the meta information sent in response to a GET request, but the HEAD verb never returns the actual resource. The meta information is cacheable.
POST : Sends data to the Web server for processing. This is typically the result of users entering data on a form and submitting that data as part of their request.
PUT :Allows a client to directly create a resource at the indicated URL on the server. The server takes the body of the request, creates the file specified in the URL, and copies the received data to the newly created file. If the file exists and is not locked, the content of the file will be overwritten.
DELETE :Used to delete a resource at the Web server. Requires write permissions on the directory.
TRACE : Used for testing or diagnostics; allows the client to see what is being received at the other end of the request chain. Responses to this method are never cached.
CONNECT :Reserved for use with a proxy that can dynamically switch to being a tun-nel, such as Secure Sockets Layer (SSL) protocol.
DEBUG Not defined in the HTTP/1.1 specification, but used to start ASP.NET debugging. This method informs Visual Studio of the process to which the debugger will attach.