F5 (normal reload) will in most browsers
re-request the page, and then request the images IF they have changed since last requested (if-modified-since / e-tag headers).
A click on a link to an already downloaded page that has proper headers set (no-cache etc.) will reload the page, but will probably NOT re-request the images. This will reduce the bandwidth for the image servers, but only by about a 300 bytes per request or so, assuming the webservers for the images are well-behaved. Ofcourse 300 bytes x 10,000 unnessisary requests per image is still 3Mb per image..
You can check this on firefox if you have HTTP headers plugin (not installed now, sorry).
( ,
Sun 18 Jul 2004, 23:06,
archived)
A click on a link to an already downloaded page that has proper headers set (no-cache etc.) will reload the page, but will probably NOT re-request the images. This will reduce the bandwidth for the image servers, but only by about a 300 bytes per request or so, assuming the webservers for the images are well-behaved. Ofcourse 300 bytes x 10,000 unnessisary requests per image is still 3Mb per image..
You can check this on firefox if you have HTTP headers plugin (not installed now, sorry).