Hi,
I would like to know how Squid handles a socket connection with a user
after the connection has been established. I'm assuming that Squid uses
the same socket to handle the requests and responses to all the objects
that make up a web page. For example, if a user requests URL A and this
page con
Bilal wrote:
>
> Hi,
> I would like to know how Squid handles a socket connection with a user
> after the connection has been established. I'm assuming that Squid uses
> the same socket to handle the requests and responses to all the objects
> that make up a web page. For example, if a user requ
Squid uses the HTTP protocol over TCP, as specified in RFC2616 and it's
predecessors.
Connections browser<->squid and squid<->servers is managed separately.
tor 2003-02-06 klockan 11.21 skrev Bilal:
> Hi,
> I would like to know how Squid handles a socket connection with a user
> after the connect
Marc Elsen wrote:
> > How does Squid know that all the objects have been requested and that
> > the socket should be closed? What determines this?
>
> It doesn't ,the browser (or client) will tell squid when it is
> finished
> asking for objects.
Squid will close the connection if the browse
> > > Is it possible for a user to request URL B, and this URL is
handled
> > > via the same socket as URL A was? How does Squid take care of
this?
>
> > That is irrelevant. In TCP two seperate connection to a remote
> > box can not use the same socket.
> Not fully. The connection may be per
mån 2003-02-10 klockan 12.36 skrev Bilal:
> If a second request for another web page can be made via the same
> socket, how common is this occurrence?
Quite common. See the cachemgr statistics.
--
Henrik Nordstrom <[EMAIL PROTECTED]>
MARA Systems AB, Sweden
