471,350 Members | 1,576 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,350 software developers and data experts.

Connection: Keep-Alive vs Connection: Close

With the sniffer ethereal I get a lot of Connections Keep Alive in some
sites like google.com and that returns me the Content-Length in the
HTTP response header.

When the connection is Close I don't get the Content-Length but I get
an hexadecimal number that represents the size of the page but that is
after the header and in the page more precisely.

Is this normal to have this behaviour? I don't know how IE does to get
Connections Keep Alive and the respective Content-Length but between
the GET and the HTTP/1.1 200 OK from the response I see a TCP fragment
that I don't receive in my application.

Does this behaviour of Connection Keep Alive and Connection Close is
part of the HTTP RFC standards? Why does Internet Explorer gets more
connections keep alive than I? What a frustrating task to do.

Any help is appreciated,
Nuno Magalhaes.

Nov 28 '05 #1
1 4913
Read the HTTP Rfc. To get keep alives browser adds specific parameters to
the HTTP header, server recognizes them and doesn't close the connection,
but sends keep-alive....

--
Vadym Stetsyak aka Vadmyst
http://vadmyst.blogspot.com
"Nuno Magalhaes" <nu************@hotmail.com> wrote in message
news:11**********************@g43g2000cwa.googlegr oups.com...
With the sniffer ethereal I get a lot of Connections Keep Alive in some
sites like google.com and that returns me the Content-Length in the
HTTP response header.

When the connection is Close I don't get the Content-Length but I get
an hexadecimal number that represents the size of the page but that is
after the header and in the page more precisely.

Is this normal to have this behaviour? I don't know how IE does to get
Connections Keep Alive and the respective Content-Length but between
the GET and the HTTP/1.1 200 OK from the response I see a TCP fragment
that I don't receive in my application.

Does this behaviour of Connection Keep Alive and Connection Close is
part of the HTTP RFC standards? Why does Internet Explorer gets more
connections keep alive than I? What a frustrating task to do.

Any help is appreciated,
Nuno Magalhaes.

Nov 28 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by Steve Jorgensen | last post: by
3 posts views Thread by Alan Wang | last post: by
reply views Thread by Mike Hoorens | last post: by
3 posts views Thread by patrickbeaudoin | last post: by
11 posts views Thread by cty0000 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.