Images not put in cache

[Guest]

Hi,

All images on my ASP.Net web site are reloaded almost each time I visit a
page. My chache setting on IE is set to Automatically. When I visit another
web site, images are rarely reloaded so it's fast. This slows down my site
and it's really a pain in the neck.

All my web pages are dynamic and are built from a database. There no meta
field or Response.Expires...

So I was wondering if ASP.Net has something to do with this? How can I force
images to be put in cache?

Test by yourself to see what I'm talking about: http://www.nuouz.com

Thanks for any help

Stephane

 

[Roy]

Hi Stephanie,

If you're using the 2.0 framework, then you're experiencing the same bug
I've been dealing with for a couple months (since we upgraded). I've
tried everything, ranging from setting NO content expiration date in IIS
to hardcoding cache settings in the web code, all to no avail.

I really do chalk it up to a bug, though it seems to be a sporadic one
as not all folks seem to have this problem. Could be an interaction bug
between 2.0 framework and web server?

-Roy

 

[Guest]

Could that be because the view state field? That's the only thing that I see
changing in all my pages.

Thanks

Stephane

 

[Roy]

Possibly. I don't see how, but possibly.
I've pretty much been forced to eliminate all but the most essential
imagery from my work sites (which fortunately don't need to be all that
"pretty" to begin with given the user-base, but still).



RE: Images not put in cache
From: Stephane

Could that be because the view state field? That's the only thing that I
see
changing in all my pages.

Thanks

Stephane

 

[Raymond]

They're being cached here okay. Though looks like several
of them are dynamic images referencing aspx files. The browser
can't cache these normally. It goes by URL, so it's going to call aspx
files each time and run them to get another stream.

Is your client computer date set right?

Another reason it may be slower is that you have too many
object references. Even when they load of the cache the
browser still needs to make a connection for each and
determine whether it needs to use the cache or re-load.
This can be expensive, especialy if the site is served from
a very distant location, nothing to do with ASP.NET here.
Looks like this is hosted somehwere in SoCal, so if it's being
used by someone in Europe it's going to be slow. For that
you need to reduce the number of object references to get
it rendered there faster.

 

[Guest]

Hi,

Thanks for your answer.

What do you mean by "you need to reduce the number of object references to get
it rendered there faster."? What is an object reference?

Thanks

Stephane

 

[Raymond]

Images, script files, all those aspx references, global style sheets,
all those are object references for which the browser needs to
make connections.