Broken Images ASP.NET/IIS Problem

  • Thread starter Thread starter Jacob
  • Start date Start date
J

Jacob

Has anybody else encountered a problem when running your asp.net
applications off your localhost and having broken image links? The weird
thing is, the links aren't really broken. The reference is correct. And
what's weirder that than, it will only do it sporadically. I can refresh
the screen and those images that were once broken are now visible but some
others may now be broken. Or sometimes they all work, sometimes none. This
leads me to believe it must be something set wrong with my IIS or something.

Any help would be great!!

Thanks,
Jacob
 
Thanks for the suggestion, but that didn't seem to do the trick. I cleared
the browser cache, history, and cookies to no avail.

Jacob
 
1> Try using a tool like www.fiddlertool.com to watch your traffic to see if
error codes are being returned.
2> Are these links using file:// or http://localhost?
3> What browser are you using? There's at least one version of IE which has
a problem with small image files, particularly if you've tweaked your HTTP
Max Connections Per Server value in the registry.

--
Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.
 
I loaded on Opera 7.23 and it seems to display every image without a
problem. So the problem must be within IE. I'll continue to check my site
design with Opera in the interim, but I still hope to solve this problem. 1)
I'll look into the tools you suggested. 2.) I'm running everything as
http://localhost/. 3.) And my Cablenut/Registry settings for
MaxConnectionsPerServer is 10. My IE version is
6.0.2800.1106.xpsp2.030422-1633.

Thanks for all your help and patience.
Jacob
 
Like I said this appears to be a browser issue. I've seen this in IE as well
and it's related to the cache settings. IE does funny things when a failure
occurs the first time you load up something...

If it works with other browsers you can rule out ASP.Net or the Web
Server...


+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
 
If you've tweaked the MaxConnectionsPerServer variable, that's almost
without question the problem. HTTP spec calls for a max of 2 connections
per server and overriding this in the registry, while possible, can cause
screwy behavior.

I used to have registry override set to 10 but I noticed exactly the problem
you describe. When I set it down to 4, the problem went away.

--
Thanks,

Eric Lawrence
Program Manager
Assistance and Worldwide Services

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Well, I owe you big-time. I reset my MaxConnectionsPerServer down to 4 and
the problem went away. I never would have found the connection without your
help.

Thanks,
Jacob
 
Back
Top