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.
|
|
|
|
HTTP Proxy Servers and Proxying
(Page 2 of 3)
Comparing Proxies and Caches
Proxying and caching are concepts
that have a number of similarities, especially in terms of the impact
that they have on basic HTTP operation. Like caching, proxying has become
more important in recent years, and also complicates HTTP in a number
of ways. The HTTP/1.1 standard includes a number of specific features
to support proxies, and also addresses a number of concerns related
to proxying.
The fact that both proxying and caching
represent ways in which basic HTTP client/server communication is changed,
combined with the ability of proxies to perform caching, sometimes leads
people to think caches and proxies are the same, when they are not.
A proxy is actually a separate element that resides in the HTTP request/response
chain, where caches can be implemented within any device in that chain,
including a proxy.
Another key way that caches and proxies
differ is that caches are used automatically when they are
enabled, where proxies are not. To use a proxy, client software must
be told to use the proxy, and supplied with its IP address or domain
name. The client then sends all requests to the proxy rather than to
the actual server that the user specifies.
Note: Most of my explanations here have focused on hardware proxy servers, but proxies are also commonly implemented as software in a client device. A software proxy performs the same tasks of processing requests and responses; it is much cheaper to implement than a hardware proxy, but cannot be shared by many devices. |
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! |
|
|
Home -
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.
|