It sounds like your browser is caching. Perhaps try setting the ImageUrl to '~/ImageHandler. Ashx?
User=' or something like that. I assume that your ImageHander. Ashx will ignore the argument, but the browser will recognize that the URL is different, and so will try to fetch it again for each new user.
That worked beautifully. I set the ImageUrl in the code behind with the url you suggested and it works perfectly now! Thank you so much!
– swolff1978 Jun 11 '09 at 16:15.
Use FireBug to check if the new image if being requested. If not, then ensure that the image returned by ImageHandler. Ashx is not cached.
You can do this by looking at the header parameters in FireBug. You want the response to expire immediately, alternatively ensure it is set to no cache. Different programming paradigms have different methods of setting the header.
Also, by inspecting the Net traffic in FireBug, you will know the cause of the problem. A simple solution has already been suggested to use query parameters to make each call unique.
It helped me lot. I was having same problem. I was displaying image from mermorystream from session U just cleared cache & it worked.
Use FireBug to check if the new image if being requested. If not, then ensure that the image returned by ImageHandler. Ashx is not cached.
You can do this by looking at the header parameters in FireBug.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.