(e-mail address removed) did eloquently scribble:
Yes,
You have an obvious point.
What about if we have only 1 response to 1 request?
So...
Let's do a mind experiment.
1. I type
http://ibm.com into my browser and hit enter
2. browser sends 1 request to ibm.com
3. server sends a bunch of data back in 1 response
The server sends back the index.html page for that 1 request.
The browser begins rendering the page, selecting fonts, setting up tables
and frames, looking up image sizes, downloading the images on the page (or
not, if images are disabled)
I'm trying to get a better understanding of step 3.
Can the server get any info out of the request which it can use?
The html page IS the real "set of requests". HTML is simple text, it
contains no graphical data within itself. Only <img> links within it. It's
those said:
Is there something in the request header which says,
"dont send images"
No, it doesn't request the image. Servers only send what is requested.
try it with wget. Just point wget at your favourite website, say...
wget slashdot.org
If you just wget an index.html page (or just point it at a website), that is
all you'll get. It won't parse the index.html page and download everything
referred to on it unless you tell it to.
--
| |What to do if you find yourself stuck in a crack|
| (e-mail address removed) |in the ground beneath a giant boulder, which you|
| |can't move, with no hope of rescue. |
|Andrew Halliwell BSc(hons)|Consider how lucky you are that life has been |
| in |good to you so far... |
| Computer Science | -The BOOK, Hitch-hiker's guide to the galaxy.|