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 Entities, Transfers, Coding Methods and Content Management
HTTP Entities and Internet Media Types
(Page 3 of 3)
Other MIME Constructs Used In HTTP
In addition to media types, HTTP
also borrows from MIME in several other ways. These include the notion
codings and the
use of a header to indicate the length of an entity.
Its important to recognize, however, that even though HTTPs
handling of Internet media is very similar to that of MIME, it is not
identical. In fact, my understanding is that there was an early proposal
that HTTP use MIME exactly as defined, but a specific decision was made
not do this. We will explore a possible reason why in the
The bottom line, however, is that
HTTPs developers chose to adopt concepts from MIME that made sense,
and left other parts out. As a result, HTTP messages are not MIME compliant,
even though you may see several headers in HTTP messages starting with
MIMEs Content- prefix. For example, even though HTTP
has a Content-Encoding header, its use is quite different from
that of MIMEs, as we will again see in the next topic. Confirmation
of the difference between HTTP and MIME can be found in the fact that
HTTP does not use the MIME-Version header that is required in
Key Concept: Even though HTTP borrows several concepts and header types from MIME, the protocol is not MIME-compliant.
|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.