aspx thread: How check if there are pages in the history that come after the current page,
Chuck,
yes, I want do something with the <body onLoad=""> event. I need check if
there are pages in the history that come after the current page,
and if there is, resubmit the request for the page.
david
----- Original Message -----
From: "Feduke Cntr Charles R" <FedukeCR@m...>
To: "ASP+" <aspx@p...>
Sent: Thursday, May 09, 2002 2:35 PM
Subject: [aspx] RE: History MetaCache
> David,
>
> Yes, you are experiencing expected operation from using the back
> button. Although this is more JavaScript than ASP.NET, you probably want
to
> do something with the <body onLoad=""> event. For example, maybe you
could
> check if there are pages in the history that come after the current page,
> and if there is, resubmit the request for the page. Honestly I hate
> JavaScript so there's not much that I can tell you.
>
> There simply has to be a better way to do this. I can't believe no
> one else has any input on this.
>
> - Chuck
>
> -----Original Message-----
> From: David Ibarra BancoSaenz [mailto:dibarra@b...]
> Sent: Wednesday, May 08, 2002 10:47 AM
> To: ASP+
> Subject: [aspx] RE: History MetaCache
>
>
> yes, I meant when users clicks back button on the browser. I need that the
> page caducate and got a fresh copy of the page from the server , but that
> it's not working.
> that pages is over IIS 5.0 (Intranet).
>
> <html>
> <head>
> <meta http-equiv="pragma" content="no-cache">
> <meta http-equiv="expires" content="0">
> <title></title>
> </head>
> ..
> ..
> ..
>
>
>
> must I set IIS in order to that work very vell ? because in IIS i have:
> (I translated from Spanish screen)
>
> [x] Enabled caducity
> ( ) caducate immediatly
> ( ) caducate after ---
> ( ) caducate on ..... (date)...
>
>
>
> thanks
> david
>
> ----- Original Message -----
> From: "Feduke Cntr Charles R" <FedukeCR@m...>
> To: "ASP+" <aspx@p...>
> Sent: Wednesday, May 08, 2002 9:23 PM
> Subject: [aspx] RE: History MetaCache
>
>
> > Are you doing something like
> >
> > javascript:history.back();
> >
> > or clicking the browser's back button? These things cause the page to
> > normally be viewed from cache instead of requested (unless the cached
page
> > had not completed its download prior to being navigated away from). If
> you
> > give the user a link to navigate "back" to the page by using the URL of
> the
> > page, because of the headers IIS sends for ASP and ASP.NET pages the
> browser
> > should request a fresh copy of the page from the server (and these
headers
> > that are set is exactly the ones you're referring to in your <meta>
tags,
> so
> > you got that right).
> >
> > This is standard expected browser operation.
> >
> > HTH,
> > - Chuck
> >
> > -----Original Message-----
> > From: David Ibarra BancoSaenz [mailto:dibarra@b...]
> > Sent: Wednesday, May 08, 2002 10:04 AM
> > To: ASP+
> > Subject: [aspx] History MetaCache
> >
> >
> > Hi,
> >
> > I have a una page with a grid (Page 1), and links in the grid in order
to
> > edit the record (another page: Page 2).
> >
> > If users go back (into Page 1) I need to reload the page in order to
show
> > the new updates, because Page 1 have old values.
> >
> > I tried this in the page with grid:
> >
> > <meta http-equiv="pragma" content="no-cache">
> > <meta http-equiv="expires" content="0">
> >
> > but it's no work. must I to do something in IIS or what is happening?
> >
> > Thanks in Advance.
> >
> >
> >
> >
> >
>
>
>
>
View Cart
