When an embedded object, such as an image, a script, a flash movie, or a style sheet is
encountered during the page rendering, a new request is submitted to the server and the result
included in the page. This is an asynchronous process meaning that the embedded assets may
be fully loaded before or after the HTML code has been completely received and/or processed.
The address is not the only information sent to the server in the request; other information (usually
hidden to the end user) is packed in the request in the form of headers. These headers may contain
glitches about the identification of the browser, the preferred languages, or the contents of a form in the
page. In the same way the response may contain some extra information in the response header, like
the content type associated with the transmitted information or some values to store in the client cookies
(a small portion of the client memory reserved to store preferences for the current navigation context).
Distributing Contents Using a Web Server
To understand how a Web Server can send contents over the HTTP protocol, you need to understand
how an HTTP address is structured.
Pages:
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444