Differences between HTTP caching in client and HTTP caching in Proxy Server

[minimee120]

Just would like to know some differences, am learning about it in class

[CimmerianX]

It's really just where the copy of the content is stored.

Think of the path taken by your PC to get web content when using a proxy.
1) Your browser makes the request.
2) Browser sends the request to the proxy.
3) Proxy relays the request to public www site.
4) public www site sends content to the Proxy.
5) Proxy sends it to your browser for display.

If you hit a site often, like Daniweb, certain static content doesn't change. Logo Image for example. If the file hasn't changed, there's no need to re-download it. right?

(Basically) Your browser can cache the logo image locally, when the requests go out for the content, there is no need to request the image file again. If you have 50 machines, each one must keep a copy of the logo in local cache after having downloaded it at least once. If the logo changes, 50 machines must pull the file again.

If the proxy is caching, then the logo is stored on the server. The 1st daniweb visitor reguests the page and the images are pulled by the proxy and now stored on the proxy. The next 49 machines that visit daniweb pull the image from the proxy instead of the daniweb host, thus saving the bandwith of pulling the image 49 more times. If the image changes, the server pulls it just once to service the 50 internal machines.

[riahc3]

Here is a intresting thought though: In now, a modern area, are proxy servers really neccesary (in the scenario you put of pulling a logo)? With all the bandwidth avaliable to most first class countries....I dont see it logical.

I agree in other scenarios though a proxy server is very important and can save a lot of bandwidth.

[lolafuertes]

Is not a bandwidth (speed) problem, is a traffic (volume) one.

Imagine an scenario: 1 web server, 100.000.000 pages accessed each day. If you put some proxies in the middle, all the static parts will flow only from the server once, then from the proxies, while the dynamic part flow always from the server.

This helps to diminish not only the traffic but the server work.

Hope this helps.

[riahc3]

Is not a bandwidth (speed) problem, is a traffic (volume) one.

Imagine an scenario: 1 web server, 100.000.000 pages accessed each day. If you put some proxies in the middle, all the static parts will flow only from the server once, then from the proxies, while the dynamic part flow always from the server.

This helps to diminish not only the traffic but the server work.

Hope this helps.

Did not think of the server workload.