Clearing up the cache for a web browser

Hi,

I’ve got an aspx page that will return an image to a client, and the image 
it returns will depend on weather on session variables, as illustrated below;

  If Session.Item("LoadNativeFile") = True Then
            Response.Clear()
            Response.WriteFile("C:\allowedimage.jpg")
        Else
            Response.Clear()
            Response.WriteFile("C:\noimage.jpg ")
        End If

The above code doesn’t refer to actual images, but there as an example.  
This code allows me dynamically send images to a either an image button, or 
active x component, so if the above code was saved in a file called 
‘examaple.aspx’ I can access it through;

. <asp:Image ID="Image1" runat="server" 
ImageUrl="http://webserver/pages/example.aspx"  />

The problem is that ‘example.aspx’ (irrelevant of its content) will always 
be saved to the ‘Local Settings\Temporary Internet Files’ folder.  The
images 
that I’m using are sensitive to the clients, so I need to clear them up off 
there disk.

I cannot find a way to do this other than to overwrite the existing 
‘example.aspx’ by using a pop-up with the same tag inside <asp:Image 
ID="Image1" runat="server"
ImageUrl="http://webserver/pages/example.aspx"  />

This way I can overwrite the cached image with a non sensitive image.

I really need to be able to clear this 1 file out of the cache without a 
pop-up, and preferably as soon as it has been loaded into the browser.

Is there a reason that you are not using a secure site?  If the images are 
sensative, your site should be using secure sockets (https).  By default, IE 
does not cache anything on a secure page, which would take care of your 

The only reason I wasn’t using https was because I was still using our test 
rig.

I’ve changed it over to https and it has solved the problem completely.

Cheers.


"merc" wrote:

> Is there a reason that you are not using a secure site?  If the images are

> sensative, your site should be using secure sockets (https).  By default,
IE 
> does not cache anything on a secure page, which would take care of your