Please Whitelist This Site?
I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.
If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.
Thanks for your understanding!
Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide
NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
|| The TCP/IP Guide|
9 TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
9 TCP/IP Key Applications and Application Protocols
9 TCP/IP File and Message Transfer Applications and Protocols (FTP, TFTP, Electronic Mail, USENET, HTTP/WWW, Gopher)
9 TCP/IP World Wide Web (WWW, "The Web") and the Hypertext Transfer Protocol (HTTP)
9 TCP/IP Hypertext Transfer Protocol (HTTP)
9 HTTP Messages, Message Formats, Methods and Status Codes
(Page 3 of 4)
Other, Less-Common Methods
The other methods defined by the
HTTP standard are not used as often, but I will describe them briefly,
as you may still encounter them from time to time.
Allows the client to request that
the server send it information about available communication options.
A URI of a resource may be specified to request information relevant
to accessing that resource, or an asterisk (*) may be used
to indicate that the query is about the server itself. The response
includes headers that give the client more details about how the server
may be accessed.
Requests that the server store the
entity enclosed in the body of the request at the URL specified in the
request line. The difference between a PUT and a POST
is that in a PUT, the URI identifies the entity in the request,
while in a POST, the URI identifies a program intended to process
the entity in the request. Thus a PUT would be used to allow
a file to be copied to a server, in the exact complement to how a GET
requests that a file be copied to the client. A POST is used
for interactive programs, as explained above.
Now, would you like people to be
able to store files on your server in the same way that they request
them? Neither would I. This is one primary reason why PUT is
not often used. It has valid uses, such as uploading content to a Web
site, and must be used with authentication in this case. However, generally
speaking, storing files on a site is more often accomplished using other
means, like FTP.
Requests that the specified resource
be deleted. This has the same issues as PUT and is not often
used for similar reasons.
Allows a client to receive back a
copy of the request that it itself sent to the server, for diagnostic
Note: In addition to the methods described above, the HTTP standard reserves the method name CONNECT for future use. An earlier version of HTTP/1.1, RFC 2068, also defined the methods PATCH, LINK and UNLINK. These were removed in the final version but reference to them is still sometimes seen.
Key Concept: Each HTTP client request specifies a particular type of action that the server perform; in HTTP, these are called not commands but rather methods. The three most common HTTP methods are GET, which prompts a server to return a resource; HEAD, which returns just the headers associated with a resource; and PUT, which allows a client to submit data to a server for processing.
|If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!|
Table Of Contents - Contact Us
The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005
© Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.