Why are website images creating multiple connections?

I am hosting a website on my intranet using IIS 5.1 and Windows XP
Pro. It is an OpenWiki(ASP, XSL) site with images from my hard drive.
When someone opens a page with images, several connections to my
server are made. I have 40 connections available but I really would
like to know why each image creates its own connection.

The connections timeout after one minute. I turned off http keep-
alives but that shut down the webserver. I think this is because I use
windows authentication.

Re: Why are website images creating multiple connections?

Each image is going to count as a "connection". Plus other elements on the
page/database.

wrote in message
news:1185998116.476448.79850@j4g2000prf.googlegroups.com...
|I am hosting a website on my intranet using IIS 5.1 and Windows XP
| Pro. It is an OpenWiki(ASP, XSL) site with images from my hard drive.
| When someone opens a page with images, several connections to my
| server are made. I have 40 connections available but I really would
| like to know why each image creates its own connection.
|
| The connections timeout after one minute. I turned off http keep-
| alives but that shut down the webserver. I think this is because I use
| windows authentication.
|

Re: Why are website images creating multiple connections?

On Aug 1, 12:55 pm, wilson4...@gmail.com wrote:
> I am hosting a website on my intranet using IIS 5.1 and Windows XP
> Pro. It is an OpenWiki(ASP, XSL) site with images from my hard drive.
> When someone opens a page with images, several connections to my
> server are made. I have 40 connections available but I really would
> like to know why each image creates its own connection.
>
> The connections timeout after one minute. I turned off http keep-
> alives but that shut down the webserver. I think this is because I use
> windows authentication.



Actually, images do not create connections, nor do IIS create
connections to send responses. HTTP Clients first open HTTP
connections to the server, which then sends the response (be it
images, text, etc) back on the same connection.

So, your question is really why the web browser is creating that many
connections to the web server to download images. And that is a
question for the web browser which the web server can hardly control.

Windows Authentication requires HTTP Keep-Alives -- it is a connection-
based authentication protocol.

Bottom line: If you cannot control the browsers on your Intranet, I
think you need to host your website on a server-SKU of Windows. You
are running out of connections due to an intentional limitation of IIS
on the client-SKU of Windows. If you also require Windows
Authentication, then you cannot turn off Keep-Alives, which means you
will quickly run out of connections with your current web browser. The
net result is that you either need to run another web server on the
client-SKU of Windows (which still has other networking limitations)
or you host websites on a server-SKU of Windows.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: Why are website images creating multiple connections?

On Aug 1, 10:49 pm, David Wang wrote:
> On Aug 1, 12:55 pm, wilson4...@gmail.com wrote:
>
> > I am hosting a website on my intranet using IIS 5.1 and Windows XP
> > Pro. It is an OpenWiki(ASP, XSL) site with images from my hard drive.
> > When someone opens a page with images, several connections to my
> > server are made. I have 40 connections available but I really would
> > like to know why each image creates its own connection.
>
> > The connections timeout after one minute. I turned off http keep-
> > alives but that shut down the webserver. I think this is because I use
> > windows authentication.
>
> Actually, images do not create connections, nor do IIS create
> connections to send responses. HTTP Clients first open HTTP
> connections to the server, which then sends the response (be it
> images, text, etc) back on the same connection.
>
> So, your question is really why the web browser is creating that many
> connections to the web server to download images. And that is a
> question for the web browser which the web server can hardly control.
>
> Windows Authentication requires HTTP Keep-Alives -- it is a connection-
> based authentication protocol.
>
> Bottom line: If you cannot control the browsers on your Intranet, I
> think you need to host your website on a server-SKU of Windows. You
> are running out of connections due to an intentional limitation of IIS
> on the client-SKU of Windows. If you also require Windows
> Authentication, then you cannot turn off Keep-Alives, which means you
> will quickly run out of connections with your current web browser. The
> net result is that you either need to run another web server on the
> client-SKU of Windows (which still has other networking limitations)
> or you host websites on a server-SKU of Windows.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //

Thanks for the info David. After some googling, I found that most
developers try
to create multiple connections to speed up page loads. Apparently IE
is supposed
to be limited to 2 connections. I think openwiki's implementation of
XSL is
what might be creating the problem/feature...Nathan