I don't think it is caching. Check that the new image on the server has a
later create date than the older, if not the older will be shown.
Test this by having 2 images, aaa.jpg, put the one with the older creation
date on the server and browse to it, now put the newer one on the server,
browse to it and the 2nd one will show, all OK.
Now rename them to bbb.jpg, first put the one with the newer creation date
on the server, browse, now the older creation date, browse, the 1st image
still shows up.
"Nathan Sokalski" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> I have been trying to find a way to prevent the images on my site from
being
> cached on the user's machine. I want to avoid this because the images used
> in an Image control often change, yet have the same name. When they are
> cached, the cached image is displayed which is not what I want. I thought
> that using
> Response.Cache.SetCacheability(HttpCacheability.NoCache)
>
> would have achieved this, but it seems to only prevent the .aspx file from
> being cached. Is there any way to prevent images from being cached as
well?
> --
> Nathan Sokalski
> (E-Mail Removed)
> http://www.nathansokalski.com/
>
>