Re: State management

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Tim,

I think the problems here is that when the user hit the "back" button on
browser, the displayed page is by default retrieved from the client's
cache(if we didn't explictitly disable the page's client cache). I think
that's why you'll find the Page_load not fired. IF the page is actually
retrieved from severside , the Page_load will surely be fired.
In addition, as for detecting whether the page is requested the first time
or specifying a version info, I think we can add a certain version field(a
timestamp) in the page's viewstate at the first request( !IsPostBack), and
if there is no such field , it means it's the first request or if the info
is different from the session's data, we need to update the page. But this
depends on the page is not retrieved from client cache when user hit "back"
button. How do you thnk of this?

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

.

Relevant Pages

  • Re: Another Scripting Hole In Microsoft IE Exposes Local Files
    ... > that a flaw in IE was more damaging than a flaw in any other browser, ... > A flaw in IE may be more damaging simply because it is more likely to hit more ... > users, certainly, but the OP was suggesting that a user hit with a flaw in IE ... > score points at all expense, and argue the point at issue. ...
    (comp.security.misc)
  • Re: OutputCache Back Button Page Expires
    ... when the user hit back on an aspx page that displayed from a postback, ... browser knows it has to repost the data to get a fresh version of the page. ... > I am having a problem with the @OutputCache page directive and Web ... The cart can be added to (or deleted ...
    (microsoft.public.dotnet.framework.aspnet)