Reponse.write problem?

[Richard]

Hello,

I'm dynamically writing out a web page using response.write. The page has
images and hyperlinks (each hyperlink points back to the same page, but with
a different parameter which specifies a larger image that is loaded). When
I first bring up the page everything is fine. Then when I click on the
hyperlinks, the page reloads but has the exact same images. The only way to
view the new images is to hit 'REFRESH'. Is there something I am missing,
some way to clear the html contents before loading the page back up?

[Joris Dobbelsteen]

Check whether your entire URL (to any resource: page or image) is really
different.
If its not, check whether the page expires immediately.

- Joris

"Richard" <ab*******@mindspring.com> wrote in message
news:ew**************@TK2MSFTNGP10.phx.gbl...

Hello,

I'm dynamically writing out a web page using response.write. The page has
images and hyperlinks (each hyperlink points back to the same page, but with a different parameter which specifies a larger image that is loaded). When I first bring up the page everything is fine. Then when I click on the
hyperlinks, the page reloads but has the exact same images. The only way to view the new images is to hit 'REFRESH'. Is there something I am missing,
some way to clear the html contents before loading the page back up?

[Richard]

Thanks for your response! The URL is different, and I've tried setting
Response.ExpiresAbsolute = System.DateTime.Now.AddSeconds(5), but that
doesn't work either. Also I've noticed, it looks like the new page is
loading up, but the previous page also loads on top of it, making it look
like there's no new page. Is there some way to just clear this out (I've
tried response.clear() but no luck).

Thanks!

"Joris Dobbelsteen" <RE********************@jAoris2k.aTth.cXx> wrote in
message news:41***********************@news.wanadoo.nl...

Check whether your entire URL (to any resource: page or image) is really
different.
If its not, check whether the page expires immediately.

- Joris

"Richard" <ab*******@mindspring.com> wrote in message
news:ew**************@TK2MSFTNGP10.phx.gbl...

Hello,

I'm dynamically writing out a web page using response.write. The page has images and hyperlinks (each hyperlink points back to the same page, but with

a different parameter which specifies a larger image that is loaded).

When

I first bring up the page everything is fine. Then when I click on the
hyperlinks, the page reloads but has the exact same images. The only way to

view the new images is to hit 'REFRESH'. Is there something I am

missing, some way to clear the html contents before loading the page back up?

[Joris Dobbelsteen]

"Richard" <ab*******@mindspring.com> wrote in message
news:uN**************@TK2MSFTNGP11.phx.gbl...

Thanks for your response! The URL is different,
Thats indeed correct, are you sure the image refered to is different too?
and I've tried setting
Response.ExpiresAbsolute = System.DateTime.Now.AddSeconds(5), but that
If you don't want caching:
Response.Caching.SetCachability(HttpCachability.No Cache)

This ensures the response is never cached (including server, proxies and
clients).

Dont use Reponse.Expires / ExpiresAbsolute, these are predicated in ASP.NET.
Use Reponse.Caching.SetExpires(System.DateTime.Now.Add Seconds(5));
Always use Reponse.Caching.<whatever> if it involves caching.
doesn't work either. Also I've noticed, it looks like the new page is
loading up, but the previous page also loads on top of it, making it look
like there's no new page. Is there some way to just clear this out (I've
tried response.clear() but no luck).
Response.Clear() works only when buffering is enabled.
You can ensure this in the <@ ... > line (first on on the page).

You might want to consider posting the (relevant) source up here...
Thanks!

<snip>

- Joris

[Joerg Jooss]

Joris Dobbelsteen wrote:

"Richard" <ab*******@mindspring.com> wrote in message
news:uN**************@TK2MSFTNGP11.phx.gbl...

Thanks for your response! The URL is different,

Thats indeed correct, are you sure the image refered to is different
too?

and I've tried setting
Response.ExpiresAbsolute = System.DateTime.Now.AddSeconds(5), but
that

If you don't want caching:
Response.Caching.SetCachability(HttpCachability.No Cache)

This ensures the response is never cached (including server, proxies
and clients).

No. A client does not need to adhere to Cache-Control headers, since a
browser history is not meant to behave like a cache -- the fact that many
browsers do is misleading.

Quoting section 13.13 of the HTTP 1.1 spec:

"History mechanisms and caches are different. In particular history
mechanisms SHOULD NOT try to show a semantically transparent view of the
current state of a resource. Rather, a history mechanism is meant to show
exactly what the user saw at the time when the resource was retrieved."
Cheers,
--
Joerg Jooss
jo*********@gmx.net