Thread: Simple view on how proxies work (inc DNS)
View Single Post
Old 16-03-2004, 15:43   #32
SMHarman
Inactive
 
Join Date: Jun 2003
Services: Cablevision
Posts: 8,305
SMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronze
SMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronzeSMHarman is cast in bronze
Re: Simple view on how proxies work (inc DNS)
Quote:
Originally Posted by mr-b
Correct - but there's a way of using even less bandwidth.

If you issue an HTTP GET and also include an If-Modified-Since header then the web server will only send you the object if it has been modified since the date that you specified. If it hasn't, it replies with HTTP/1.1 304 Not Modified and then you can mark your content as being fresh again having only transferred a few bytes.

You can view this in a trace by seeing lots of 304 responses typically coming back after you hit browser Refresh.

But now we're getting away from the 'simple' aspect of this thread ...
There are some well formatted caches and browsers out there. Looking at my site stats about 25% of traffic is 304'd. That saves me a good bit in bandwidth costs.
SMHarman is offline   Reply With Quote