Re: HTTP header processing sequence

Yes, have a look at the referenced URL. It shows exactly what is going on.
The browser is not issuing a bunch of GETs and then pairing them up with the
responses.
The tool you are using. HTTPWatch is doing that, not the browser.
The browser issues a GET waits for response (no more GETs till it gets that
response)
HTTPWatch is obviously storing up the GETs and INTERNALLY to the program, is
keeping references from the GETs to the response so when you click on a GET,
HTTPWatch is showing the corresponding response that it linked to
internally.

HTTPWatch is not showing you the exact flow.

"Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> wrote in message
news:uQyEiUAeGHA.3348@xxxxxxxxxxxxxxxxxxxxxxx
Look as example at http://www.microsoft.com/msj/archive/S25F.aspx
Arkady

"Josh" <no_spam@xxxxxxxxxx> wrote in message
news:%23eeDAZ3dGHA.4932@xxxxxxxxxxxxxxxxxxxxxxx
Roger

Thanks for this. I understand how basic functionality, but my question is
more about how the browser match up all the responses send from the
server from the client.

I have installed an IE extension that allows you to view all the requests
made for a specific web page. Initially it sends the request for the html
source (or initial url specified), and if there are any more objects to
request (such as images etc) it does so, and then wait for the server to
reply sending back the requested data using appropriate headers.

I am still unclear as to the exact sequence this is processed. How does
the (browser) client know how to match up multiple received responses
from the server with GET-requests, as this does not appear to be
sequential. If you had exactly one GET-request, you could assume that the
HTTP/1.1 200 OK header received corresponds to that, but what happens to
multiple GET-requests?

If you looked at TCP headers, you could determine this via specific field
values (counters or id numbers?) that match up send and recv packets, but
is this the same for http headers? (Since we're not looking at raw TCP as
this is very low level)

TIA

Roger Hunen wrote:

The browser opens a TCP connection to the server, sends a HTTP request
and waits for the server response (status + data) before sending the
next
request. So the association of request and response is no problem.

The browser may send another request over the same TCP connection
once the response to the previous request has been received and/or may
open multiple connections to the same server.

Regards,
-Roger
--
E-mail: rhunen@xxxxxxxxx
Home: http://www.xs4all.nl/~rhunen
ADSL: http://adsl.hunen.net




.

Relevant Pages

  • Re: NotificationSampleWebDav-Monitor OWA Inbox
    ... re-login or update your cookie with each response you get... ... Warning: Exiting Action with an exception: The remote server returned an ... // Create request object and assign credentials. ... Stream newStream = Request.GetRequestStream; ...
    (microsoft.public.exchange.applications)
  • Re: Response.Flush: Differences between IIS 6.0 and 5.0?
    ... I do not expect my ASP script to continue running until the ... ASP did send the entire response buffer to the client prior to continuing ... 'See how long it takes to Flush to the browser ... Browsing to this ASP page hosted on an IIS 5.0 server yield the following ...
    (microsoft.public.inetserver.iis)
  • Re: BASIC authentication Issues with IE - Part II - Solved but WHY?
    ... We have complete control of the Request and Response ... it is up to the browser to send the credentials. ... ASP runs internally on the server. ...
    (microsoft.public.inetserver.iis.security)
  • Re: HTTP header processing sequence
    ... more about how the browser match up all the responses send from the server ... Initially it sends the request for the html ... So the association of request and response is no problem. ...
    (microsoft.public.win32.programmer.networks)
  • Re: client gets always every first time for every page a 401
    ... only the first request get 401. ... Why does my Browser in case 5 not submit the Basic Authorization String ... credentials as used in 3, because they have the same root. ... Explorer has established a connection with the server by using Basic or NTLM ...
    (microsoft.public.inetserver.iis.security)
Loading